> >> Option 2) We can precompile our pre-writtern jasper reports at build >> time, eliminating the need for run-time compilation. This does have the >> undesired side effect that admins will not be able to upload their own >> reports, which we would need to compile at run time. There are ways >> around this, such as providing a way for them to precompile the reports >> and then upload them. > >If it was up to me, I would go with this option. >I do not think that there is a big benefit in admins uploading the >templates anyway. Current jasper patch doesn't provide any UI that would >allow people to set reports parameter (right?), so uploading the templates >is has a very limited application anyway.
+1 Given it took so long to get to this point I agree that for the next release we limit ourselves to a set of pre-compiled reports. It is my expectation that once this patch is in we will have to look at and likely tune the reports that are currently in the patch. Allowing the admin to create new reports is then something we can consider for a later release --martin > >> >> Option 3) Maybe a future version of Jasper will provide a more friendly >> way to handle compilation. I have not checked into more recent versions >> that the one we are currently using. >> > > >> >> So, there it is. Thoughts and/or suggestions? >> >> Kevin >> _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
