2013/9/20 Lukas Eder <[email protected]> > > 2013/9/18 Stéphane Cl <[email protected]> > >> Hello, >> I know there have been many discussions on this list regarding a possible >> better, more decoupled code generation engine in the future but it seems >> that the old not-so-good system is still going to be there for some time. >> Therefore, I would like to suggest one or two improvements. >> >> First, regarding the XML file you need to specify in the command line, I >> think would be nice if you could use java properties to avoid hardcoding >> some of the values. >> >> <jdbc> >> <driver>${jdbc.driver}</driver> >> <url>${jdbc.url}</url> (...) >> </jdbc> >> >> this would allow you to specify some of them using -Dargs in the command >> line and make your XML file more portable. After all, the XML file is >> likely to be included in version control and it should be interesting to >> run it from any machine, encapsulating specific disk path and jdbc settings >> in an appropriate shell script. >> > > I understand your concerns. Unfortunately, properties-based code generator > configuration is quite hard to maintain (think of forced types, etc.) and > was thus removed with jOOQ 3.0 ("ant task"): > http://www.jooq.org/doc/3.1/manual/reference/migrating-to-3.0/#N13700 > > You can, of course, provide the code generator with programmatic > configuration. At code gen build time, the XSD ( > http://www.jooq.org/xsd/jooq-codegen-3.0.0.xsd) is used by an XJC task to > produce JAXB-annotated artefacts. In other words, you can unmarshal the XML > yourself, using JAXB, and then patch relevant parts programmatically, > passing the org.jooq.util.jaxb.Configuration object to > the org.jooq.util.GenerationTool.main(Configuration) method. > > >> Second, I think it is currently a pain to implement a default generator >> to say "I want this java name for this sql field/table/record" and (I mean >> no offense, really!) it's not *extremely well documented*, would it be >> possible to configure that from xml? >> > > I am aware of the lack of documentation in this section. I guess your hint > is the "last straw", to make me add some sections right now :-) >
Also, some heads-up regarding *what* can be improved would be greatly appreciated. I've had lots of feedback about the documentation being insufficient. So, what's missing? What would ease the pain most? > > Improvements to the XML configuration in this area are on the roadmap: > https://github.com/jOOQ/jOOQ/issues/1171 > > Contributions towards such requirements would be welcome, of course. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
