IREPORT, Hibernate Annotations, wasting all kinds of time
I was very excited to tryout IReport with Hibernate annotations. I've been using Hibernate Annotations for over a year now and I'm absolutely in love with them. I saw that IReport which is apparently a great way to create Jasper Reports, supported Hibernate with Annotations. After downloading, installing, I started up the app and was ready to be impressed.
Unfortunately, apparently, there is a bug which either makes this impossible http://www.jasperforge.org/sf/go/artf2703?nav=1, or if there is a solutions, Jasper Forge doesn't feel like sharing.
I'm really not sure why this would be. I see this periodically. One person reports a problem, then responses show up that are irrelevant, the original reporter plays along, but finally, no solutions are offered and the post goes dark. I can understand this sometimes, but when you're reporting a possible bug and the programming who is reporting it is obviously credible (as in the above post), why just go dark? If you really don't have an answer, then say so. If your a programmer on the project, have the curtsy to say "Hey, we're looking into it". Going dark is really the worst thing. It says to me "Gosh, we don't know and we don't care, we would care if it was easy to fix, but since it isn't...".
Should I buy the documentation? I thought about it, but what if IReport just doesn't plain work with Hibernate Annotations? Then what? Not only did I waste money and time I still don't have my solution.
Should I download the source code and try to fix it? Well, gosh, maybe, but what if someone is actually fixing this or there isn't a problem, just a simple configuration issue? Then I should have bought the docs instead.
by the way, I did try to contact Jasper Forge, but to no avail...
Oh well, on to something other than IReports, maybe next year...
Unfortunately, apparently, there is a bug which either makes this impossible http://www.jasperforge.org/sf/go/artf2703?nav=1, or if there is a solutions, Jasper Forge doesn't feel like sharing.
I'm really not sure why this would be. I see this periodically. One person reports a problem, then responses show up that are irrelevant, the original reporter plays along, but finally, no solutions are offered and the post goes dark. I can understand this sometimes, but when you're reporting a possible bug and the programming who is reporting it is obviously credible (as in the above post), why just go dark? If you really don't have an answer, then say so. If your a programmer on the project, have the curtsy to say "Hey, we're looking into it". Going dark is really the worst thing. It says to me "Gosh, we don't know and we don't care, we would care if it was easy to fix, but since it isn't...".
Should I buy the documentation? I thought about it, but what if IReport just doesn't plain work with Hibernate Annotations? Then what? Not only did I waste money and time I still don't have my solution.
Should I download the source code and try to fix it? Well, gosh, maybe, but what if someone is actually fixing this or there isn't a problem, just a simple configuration issue? Then I should have bought the docs instead.
by the way, I did try to contact Jasper Forge, but to no avail...
Oh well, on to something other than IReports, maybe next year...
posted by Unknown at 11:56 AM
5 Comments:
Have you found a solution for this?
I checked the book you mentiond and I does not say anything about annotations... It just expects hbm files.
Well, I'm in the same boat. Using Hibernate Annotations and trying out iReport. Still can't locate a post nor a site that indicates how to get them to play well together.
Have you found a hint on this problem yet?
Thx
ARGH! I, too, am attempting to get this working. There is an active thread on the iReport forum about it, but no solution yet, except the need to rebuilt the damn thing.
Did u find the solution yet?
cause I'm trying to do the same.
I did not find a solution, sorry, I gave up using IReport.
Post a Comment
<< Home