Hi Geert. At my work place, we're facing the challenge of having to generate Jasper report files (.jrxml files) on the fly based on various parameters.
The report files are so painful and inhumane to work with that I'll refrain from describing it in further detail here. So we came up the idea of using a template engine to generate these files - trick in this approach is that the oddities in the jrxml files will be handled programatically by our "template controller", and enabling us to let a user decide what columns he want to see in the report using some (web) interface. Now, that may sound confusing (and it is), but we're confident that we can make it work; *provided* we find a template engine that is: * support template composition or inheritence (like the one in RIFE, hence this mail) * easy to pick up and use * and dosn't inforce an application architecture or other kinds nasty constraints. Now, most template engines are specialised to build web pages. This is not an inherent problem since we will be generating XML anyway. However; it is important that we can somehow conrtol it - library style, rather than framework style. For instance, if the template engine is tightly coupled with the servlet-api, or some such ballchain, then it will likely be a no-go for us. So here's the question (at last): Can I with relative ease use just the template engine from RIFE, without having the full package forced down my throad? Or even better; can I rip it out of RIFE and put it in a JAR for it self? -- Venlig hilsen / Kind regards, Christian Vest Hansen. _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
