Automating your Code Generation
XMLBeans provides a nifty code generator (scomp) that creates Java POJOs to represent XML Schema Types from XSD documents. You can run scomp from the command line, an ant build file, but if you work within the context of Maven projects, I recommend taking advantage of the XMLBeans mojo
As with most things maven, if you follow the standard conventions, things just work. The trick to setting up your pom.xml to execute your code generation is to fit into the convention, and in this case it is not that difficult.
Keeping the source around
I happen to like having the generated source code in the context of my projects, and scomp lets you specify where you want it to place the source it generates. Maven has conventions around the directory structure for your source code, so we need to ensure our source goes to the right place – in this case it would be
Generated code should be “throwaway”, in other words we should be able to safely delete it, and run the code generator again. We can specify in our pom.xml that we would like to have the generated sources removed as part of the clean process. We do this by configuring the maven-clean-plugin.
Now the sources will be cleaned out prior to any code generation.
Generating the Java Source
Now we can configure the XMLBeans plugin to do our bidding. First we tell Maven we want it to run at all – the plugin “plugs” itself into the proper lifecycle events in Maven so you don’t have to worry about that. Then it’s a matter of providing scomp with the appropriate options. Here again there are conventions that are good to follow, for example you may note the schema directory location and the .xsdconfig file location.
Overriding the Package Names
By default, XMLBeans uses the schema namespace as inspiration for creating your Java package names. In some cases this works well, but a schema designer may not take Java developer usability into account when creating XSD documents. For example, you may not appreciate a package name of “com.mylongcompanyname.services.public.purchaseorders.v356”, and would prefer something like “com.mylongcompanyname.po”. Happily, scomp will grant your wish by honouring any overrides you have defined in an xsdconfig file. In this case, we would create a file (xmlbeans.xsdconfig) with the following content:
Now you can run “mvn clean install” on your pom and marvel at the automation you just implemented.