I've been using Jasper reports for some time and had a few successes.
I *did* manage to create a framework whereby reports could be uploaded, configured and run in a webapp without needing to write any java code, or redeploy the application. This was great news as I was able to offload a bunch of report writing tasks to semi-technical Business Analyists (with just a smattering of SQL knowledge and a good understanding of our underlying data model) - instead of burdening the development team.
I'm now in a new role, with a new organisation who want to achieve the same sort of thing. I have to come to terms with a whole bunch of new frameworks and environments that are new to me including the using Spring/Hibernate.
The data structures in my new organisation seem to be a closely held secret. DB tables are not created from scripts, but generated from annotated Hibernate beans. There is a deep-seated reluctance to attach the Database and developers work purely in the object world (which I can see has advantages).
The problem as I see it is that to use a Hibernate datasource in a Jasper report (PLEASE correct me if I'm wrong!) - Instead of the query being defined in SQL in the jrxml - it seems to be determined in a java JRDataSource class.
Does this mean that I can forget the idea of creating new reports without needing to write any java code?
Is this assumption correct? Is there no way to write a 'code free' Jasper Report using a Hibernate datasource?
If you live in a cold climate and on the grid, incandescent light can use less energy than LED. Tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss