Call me an old school Java developer but I like layers of separation. I like the generated POJO classes to be decoupled as possible and they fairly are but...
The current code generator will do several things I don't like. 1. Make POJO classes with the exact same name as the Table objects. 2. I don't like having POJO in the package name. We use package names for all kinds of things (routing, metrics) so it is ugly to see pojo. 3. Mix the POJO classes in the same hierarchy as the Table / Record classes. 4. If using the Maven generator all of the above will be in the same Jar (ideally the pojos would be in their own jar). Thus I have written a code generator that will put all the POJOs into a data package and everything else will go into an internal package. com.mycompany.data <--- pojos live here com.mycompany.internal <-- database tables (the subpackages are the same). https://gist.github.com/agentgt/221f76b5d3ed49272ef467c0e2143069 Sadly I haven't figured out an effective way to separate the classes into separate Jars easily with out rerunning the generator and doing some maven hacks. However there are ways to exclude package names (ie ban other maven modules from using *.internal): http://stackoverflow.com/questions/7467756/maven-plugin-to-restrict-specific-packages-from-being-used -- 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/d/optout.
