Thank you, Jacques: I have spent a lot of time enhancing the framework to make this possible and taking design decisions to isolate birt code into one component, so I truly appreciate your comment. I think that with this new layout the birt component, when moved to extras, will be easy to enhance and free to evolve accordingly to the desires of the maintainers of it; for example, they could decide to split it into two hot-deploy components: birt (with framework code) and birtappls (with reports) or similar.
Jacopo On Jul 13, 2012, at 12:08 PM, Jacques Le Roux wrote: > Thanks for the effort Jacopo, > > Really appreciated! > > Jacques > > From: <[email protected]> >> Author: jacopoc >> Date: Fri Jul 13 09:48:32 2012 >> New Revision: 1361130 >> >> URL: http://svn.apache.org/viewvc?rev=1361130&view=rev >> Log: >> Moved the "birt" component out of framework to specialpurpose; moved all the >> birt reports from the applications to the birt component itself, where the >> application webapps are overriden to inject the reports; the end result is >> the same but since all these birt reports are simply a proof of concepts >> that cannot be used in production (for example they use hardcoded userlogin >> for authentication) the birt component should be probably disabled by >> default (but this will be discussed in the dev list). >> Now it will be very easy to extract the birt component (for OFBiz Extras) or >> to disable it when deploying to production or when interested in sparing >> some hardware resources. I did some cursory tests but since the work has >> been challenging and rather complex I would appreciate testing help and also >> reviews to finds chunks of code that I could have missed and that could be >> moved out as well. >
