Just one caveat about the article: as far as I remember creating a platform and report engine were costly operations. I do not have the code at hand but I remember we created some kind of singleton that was used to launch the reports. Additionally we added some logic that would: 1-scan report for parameters and generate an UI based on that. 2-replace "design" data-sources for "production" data-sources. 3-For images and other resources there was some interface you could implement so that reports could be able to call-back to the server and get them served. We rolled out our own implementation and plugged it into BIRTs machinery.
Ernesto On Thu, Oct 15, 2009 at 9:57 AM, Peter Thomas <[email protected]> wrote: > there was this article on DZone recently on integrating BIRT with Wicket, > may be useful > > http://java.dzone.com/articles/integrating-birt-your-wicket > > > On Thu, Oct 15, 2009 at 12:48 PM, Ernesto Reinaldo Barreiro < > [email protected]> wrote: > > > I have used it in combination with BIRT. But, there was nothing special > on > > the Wicket side, except for: > > 1-some logic that would read REPORT parameters and dynamically build a > form > > allowing to fill in those. > > 2-extended BIRT with some classes, implementing some BIRT interfaces, > that > > would stream back images > > when rendering HTML reports. > > > > Best, > > > > Ernesto > > > > On Wed, Oct 14, 2009 at 6:08 PM, Douglas Ferguson < > > [email protected]> wrote: > > > > > Hey, > > > > > > I'm starting to look into reporting frameworks and was curious if > > > anybody had successfully integrated with wicket? > > > > > > Are there any "off the shelf" integrations or will I have to roll my > > > own? > > > > > > D/ > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
