Yep, when I look back at the log it does emit a warning. But its part of a maven build, so it just kind of gets lost in the noise. Nice that there is a java approach, but I like the XML.
Darren On Tue, Jan 28, 2014 at 5:52 AM, Lukas Eder <[email protected]> wrote: > > 2014-01-27 Darren S <[email protected]> > >> Oh, I feel like an idiot now. So the problem is that I had two >> customTypes elements, not one customTypes element with two customType in it. > > > It happens to the best :-) > But did the jOOQ code generator emit a warning? There should be warnings in > the logs when you provide invalid XML, as jOOQ uses a > javax.xml.bind.ValidationEventHandler when unmarshalling the XML. > > Another option to avoid such mistakes, of course, is to use programmatic > configurations: > http://www.jooq.org/doc/3.2/manual/code-generation/codegen-programmatic/ > > Cheers > Lukas > > -- > You received this message because you are subscribed to a topic in the > Google Groups "jOOQ User Group" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jooq-user/CuyJmQOl8HI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- 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.
