Subject:More flexible generated Java code Author:Andrew Howard Date:08 Aug 2007 02:00 AM
I have a generated Java class for a pipeline, that I want to embed in a Spring application. The location of XQuery files can be defined via the setBaseUri method, but the location of the .pipeline file and the database connection details are hard coded. Included below are some examples from my pipeline code.
The location of the .pipeline file will change between development and production and the database details need to be passed in. Is it possible to modify the generation template to make the object completely relocatable?
Due to Spring, my preference would be for the generated object to use the JavaBean convention and have these hard-coded values replaced by bean properties.
I can, of course, hand edit the generated Java code, but I really want to minimise manual intervention and just drop these generated objects(plus query files) into a larger project and have it compiled in as is.
Is this something that can be done now - or is this a new feature request?