How can I tell jaxb Maven to generate multiple schema packages

Question

Example    lt  plugin gt                 lt plugin gt              lt groupId gt org jvnet jaxb2 maven2 lt  groupId gt              lt artifactId gt maven-jaxb2-plugin lt  artifactId gt              lt version gt 0 7 1 lt  version gt              lt executions gt                lt execution gt                  lt goals gt                    lt goal gt generate lt  goal gt                  lt  goals gt                lt  execution gt              lt  executions gt               lt configuration gt                lt schemaDirectory gt src main resources dir1 lt  schemaDirectory gt                 lt schemaIncludes gt                     lt include gt schema1 xsd lt  include gt                 lt  schemaIncludes gt                 lt generatePackage gt schema1 package lt  generatePackage gt              lt  configuration gt            lt  plugin gt             lt plugin gt              lt groupId gt org jvnet jaxb2 maven2 lt  groupId gt              lt artifactId gt maven-jaxb2-plugin lt  artifactId gt              lt version gt 0 7 1 lt  version gt              lt executions gt                lt execution gt                  lt goals gt                    lt goal gt generate lt  goal gt                  lt  goals gt                lt  execution gt              lt  executions gt               lt configuration gt                lt schemaDirectory gt src main resources dir2 lt  schemaDirectory gt                 lt schemaIncludes gt                     lt include gt schema2 xsd lt  include gt                 lt  schemaIncludes gt                 lt generatePackage gt schema2 package lt  generatePackage gt              lt  configuration gt            lt  plugin gt          lt  plugins gt    What happened  Maven executes the the first plugin  Then deletes the target folder and creates the second package  which then is visible   I tried to set target somedir1 for the first configuration and target somedir2 for the second configuration  But the behavior does not not change  Any ideas  I do not want to generate the packages directly in the src main java folder  because these packages are genereated and should not be mixed with manual created classes

User · Answer

This is fixed in version 1 6 of the plugin                lt groupId gt org codehaus mojo lt  groupId gt               lt artifactId gt jaxb2-maven-plugin lt  artifactId gt               lt version gt 1 6 lt  version gt    Quick note though  I noticed that the first iteration output was being deleted  I fixed it by adding the following to each of the executions                            lt removeOldOutput gt false lt  removeOldOutput gt                           lt clearOutputDir gt false lt  clearOutputDir gt    Here is my full working example with each iteration outputting correctly  BTW I had to do this due to a duplicate namespace problem with the xsd s I was given  This seems to resolve my problem            lt plugin gt               lt groupId gt org codehaus mojo lt  groupId gt               lt artifactId gt jaxb2-maven-plugin lt  artifactId gt               lt version gt 1 6 lt  version gt               lt executions gt                   lt execution gt                       lt id gt submitOrderRequest lt  id gt                       lt goals gt                           lt goal gt xjc lt  goal gt                       lt  goals gt                       lt configuration gt                           lt extension gt true lt  extension gt                           lt schemaDirectory gt src main resources xsd  lt  schemaDirectory gt                           lt  --  lt schemaFiles gt getOrderStatusResponse xsd quoteShippingRequest xsd quoteShippingResponse xsd submitOrderRequest xsd submitOrderResponse xsd lt  schemaFiles gt  -- gt                           lt schemaFiles gt submitOrderRequest xsd lt  schemaFiles gt                           lt bindingDirectory gt   project basedir  src main resources xjb lt  bindingDirectory gt                           lt bindingFiles gt submitOrderRequest xjb lt  bindingFiles gt                           lt removeOldOutput gt false lt  removeOldOutput gt                           lt clearOutputDir gt false lt  clearOutputDir gt                       lt  configuration gt                   lt  execution gt                   lt execution gt                       lt id gt submitOrderResponse lt  id gt                       lt goals gt                           lt goal gt xjc lt  goal gt                       lt  goals gt                       lt configuration gt                           lt extension gt true lt  extension gt                           lt schemaDirectory gt src main resources xsd  lt  schemaDirectory gt                           lt  --  lt schemaFiles gt getOrderStatusResponse xsd quoteShippingRequest xsd quoteShippingResponse xsd submitOrderRequest xsd submitOrderResponse xsd lt  schemaFiles gt  -- gt                           lt schemaFiles gt submitOrderResponse xsd lt  schemaFiles gt                           lt bindingDirectory gt   project basedir  src main resources xjb lt  bindingDirectory gt                           lt bindingFiles gt submitOrderResponse xjb lt  bindingFiles gt                           lt removeOldOutput gt false lt  removeOldOutput gt                           lt clearOutputDir gt false lt  clearOutputDir gt                       lt  configuration gt                   lt  execution gt               lt  executions gt            lt  plugin gt

User · Answer

i have solved with                            lt removeOldOutput gt false lt  removeOldOutput gt                           lt clearOutputDir gt false lt  clearOutputDir gt                           lt forceRegenerate gt true lt  forceRegenerate gt    add this to each configuration

User · Answer

I had to specify different generateDirectory  without this  the plugin was considering that files were up to date and wasn t generating anything during the second execution   And I recommend to follow the target generated-sources  lt tool gt  convention for generated sources so that they will be imported in your favorite IDE automatically  I also recommend to declare several execution instead of declaring the plugin twice  and to move the configuration inside each execution element     lt plugin gt     lt groupId gt org jvnet jaxb2 maven2 lt  groupId gt     lt artifactId gt maven-jaxb2-plugin lt  artifactId gt     lt version gt 0 7 1 lt  version gt     lt executions gt       lt execution gt         lt id gt schema1-generate lt  id gt         lt goals gt           lt goal gt generate lt  goal gt         lt  goals gt         lt configuration gt           lt schemaDirectory gt src main resources dir1 lt  schemaDirectory gt           lt schemaIncludes gt             lt include gt shiporder xsd lt  include gt           lt  schemaIncludes gt           lt generatePackage gt com stackoverflow package1 lt  generatePackage gt           lt generateDirectory gt   project build directory  generated-sources xjc1 lt  generateDirectory gt         lt  configuration gt       lt  execution gt       lt execution gt         lt id gt schema2-generate lt  id gt         lt goals gt           lt goal gt generate lt  goal gt         lt  goals gt         lt configuration gt           lt schemaDirectory gt src main resources dir2 lt  schemaDirectory gt           lt schemaIncludes gt             lt include gt books xsd lt  include gt           lt  schemaIncludes gt           lt generatePackage gt com stackoverflow package2 lt  generatePackage gt           lt generateDirectory gt   project build directory  generated-sources xjc2 lt  generateDirectory gt         lt  configuration gt       lt  execution gt     lt  executions gt   lt  plugin gt    With this setup  I get the following result after a mvn clean compile     tree target  target   -- classes         -- com                -- stackoverflow                    -- App class                    -- package1                           -- ObjectFactory class                           -- Shiporder class                           -- Shiporder Item class                           -- Shiporder Shipto class                    -- package2                        -- BookForm class                        -- BooksForm class                        -- ObjectFactory class                        -- package-info class         -- dir1                -- shiporder xsd         -- dir2             -- books xsd  -- generated-sources      -- xjc             -- META-INF                 -- sun-jaxb episode      -- xjc1             -- com                 -- stackoverflow                     -- package1                         -- ObjectFactory java                         -- Shiporder java      -- xjc2          -- com              -- stackoverflow                  -- package2                      -- BookForm java                      -- BooksForm java                      -- ObjectFactory java                      -- package-info java   Which seems to be the expected result

User · Answer

you should change that to define the plugin only once and do twice execution areas   like the following   and the generateDirectory should be set  based on the docs      lt plugin gt     lt groupId gt org jvnet jaxb2 maven2 lt  groupId gt     lt artifactId gt maven-jaxb2-plugin lt  artifactId gt     lt version gt 0 7 1 lt  version gt     lt executions gt       lt execution gt         lt id gt firstrun lt  id gt         lt goals gt           lt goal gt generate lt  goal gt         lt  goals gt         lt configuration gt           lt generateDirectory gt target gen1 lt  generateDirectory gt           lt schemaDirectory gt src main resources dir1 lt  schemaDirectory gt           lt schemaIncludes gt             lt include gt schema1 xsd lt  include gt           lt  schemaIncludes gt           lt generatePackage gt schema1 package lt  generatePackage gt         lt  configuration gt       lt  execution gt       lt execution gt         lt id gt secondrun lt  id gt         lt goals gt           lt goal gt generate lt  goal gt         lt  goals gt         lt configuration gt           lt generateDirectory gt target gen2 lt  generateDirectory gt           lt schemaDirectory gt src main resources dir2 lt  schemaDirectory gt           lt schemaIncludes gt             lt include gt schema2 xsd lt  include gt           lt  schemaIncludes gt           lt generatePackage gt schema2 package lt  generatePackage gt         lt  configuration gt       lt  execution gt     lt  executions gt   lt  plugin gt    It seemed to me that you are fighting against single artifact rule of maven   may be you should think about this

User · Answer

There is another  a clear one  IMO  solution to this There is a parameter called  staleFile  that uses as a flag to not generate stuff again  Simply alter it in each execution

User · Answer

This can also be achieved by specifying stale file name for schemas and not clearing output directory  The default out put directory is automatically included in classpath which is little convenient  If we specify different output directory one has to take care of classpath to use this code in IDE  For example -   lt plugins gt           lt plugin gt               lt groupId gt org codehaus mojo lt  groupId gt               lt artifactId gt jaxb2-maven-plugin lt  artifactId gt               lt version gt 1 3 1 lt  version gt               lt configuration gt                   lt quiet gt true lt  quiet gt                   lt verbose gt false lt  verbose gt                   lt clearOutputDir gt false lt  clearOutputDir gt                   lt readOnly gt true lt  readOnly gt                   lt arguments gt -mark-generated lt  arguments gt               lt  configuration gt               lt executions gt                   lt execution gt                       lt id gt reportingSchema lt  id gt                       lt goals gt                           lt goal gt xjc lt  goal gt                       lt  goals gt                       lt configuration gt                           lt schemaDirectory gt src main resources schema r17 schemaReporting lt  schemaDirectory gt                           lt schemaIncludes gt                               lt include gt OCISchemaReporting xsd lt  include gt                           lt  schemaIncludes gt                           lt packageName gt com broadsoft oci r17 reporting lt  packageName gt                           lt staleFile gt   build directory  generated-sources  jaxb-staleFlag-reporting lt  staleFile gt                       lt  configuration gt                   lt  execution gt                   lt execution gt                       lt id gt schemaAS lt  id gt                       lt goals gt                           lt goal gt xjc lt  goal gt                       lt  goals gt                       lt configuration gt                           lt schemaDirectory gt src main resources schema r17 schemaAS lt  schemaDirectory gt                           lt schemaIncludes gt                               lt include gt OCISchemaAS xsd lt  include gt                           lt  schemaIncludes gt                           lt packageName gt com broadsoft oci r17 as lt  packageName gt                           lt staleFile gt   build directory  generated-sources  jaxb-staleFlag-as lt  staleFile gt                       lt  configuration gt                   lt  execution gt               lt  executions gt           lt  plugin gt   lt  plugins gt    Source Generating Code with JAXB Plugin

User · Answer

You can use also JAXB bindings to specify different package for each schema  e g     lt jaxb bindings xmlns jaxb  http   java sun com xml ns jaxb  xmlns xjc  http   java sun com xml ns jaxb xjc      xmlns xs  http   www w3 org 2001 XMLSchema  version  2 0  schemaLocation  book xsd  gt        lt jaxb globalBindings gt           lt xjc serializable uid  1    gt       lt  jaxb globalBindings gt        lt jaxb schemaBindings gt           lt jaxb package name  com stackoverflow book    gt       lt  jaxb schemaBindings gt    lt  jaxb bindings gt    Then just use the new maven-jaxb2-plugin 0 8 0  lt schemas gt  and  lt bindings gt  elements in the pom xml  Or specify the top most directory in  lt schemaDirectory gt  and  lt bindingDirectory gt  and by  lt include gt  your schemas and bindings    lt schemaDirectory gt src main resources xsd lt  schemaDirectory gt   lt schemaIncludes gt       lt include gt book   xsd lt  include gt       lt include gt person   xsd lt  include gt   lt  schemaIncludes gt   lt bindingDirectory gt src main resources lt  bindingDirectory gt   lt bindingIncludes gt       lt include gt book   xjb lt  include gt       lt include gt person   xjb lt  include gt   lt  bindingIncludes gt    I think this is more convenient solution  because when you add a new XSD you do not need to change Maven pom xml  just add a new XJB binding file to the same directory

User · Answer

The following works for me  after much trial   lt plugin gt            lt groupId gt org codehaus mojo lt  groupId gt            lt artifactId gt jaxb2-maven-plugin lt  artifactId gt            lt version gt 2 1 lt  version gt            lt executions gt               lt execution gt                 lt id gt xjc1 lt  id gt                 lt goals gt                     lt goal gt xjc lt  goal gt                 lt  goals gt                lt configuration gt                   lt packageName gt com mycompany clientSummary lt  packageName gt                  lt sourceType gt wsdl lt  sourceType gt                   lt sources gt                   lt source gt src main resources wsdl GetClientSummary wsdl lt  source gt                   lt  sources gt                   lt outputDirectory gt target generated-sources xjb lt  outputDirectory gt                    lt clearOutputDir gt false lt  clearOutputDir gt               lt  configuration gt             lt  execution gt              lt execution gt                lt id gt xjc2 lt  id gt                lt goals gt                    lt goal gt xjc lt  goal gt                lt  goals gt                lt configuration gt                   lt packageName gt com mycompany wsclient employerProfile lt  packageName gt                   lt sourceType gt wsdl lt  sourceType gt                   lt sources gt                   lt source gt src main resources wsdl GetEmployerProfile wsdl lt  source gt                   lt  sources gt                   lt outputDirectory gt target generated-sources xjb lt  outputDirectory gt                   lt clearOutputDir gt false lt  clearOutputDir gt            lt  configuration gt            lt  execution gt             lt execution gt               lt id gt xjc3 lt  id gt               lt goals gt                   lt goal gt xjc lt  goal gt               lt  goals gt               lt configuration gt                   lt packageName gt com mycompany wsclient producersLicenseData lt  packageName gt                   lt sourceType gt wsdl lt  sourceType gt                   lt sources gt                   lt source gt src main resources wsdl GetProducersLicenseData wsdl lt  source gt                   lt  sources gt                   lt outputDirectory gt target generated-sources xjb lt  outputDirectory gt                   lt clearOutputDir gt false lt  clearOutputDir gt               lt  configuration gt           lt  execution gt          lt  executions gt     lt  plugin gt

User · Answer

I encountered a lot of problems when using jaxb in Maven but i managed to solve your problem by doing the following  First create a schema xjc file   lt  xml version  1 0  encoding  UTF-8   gt   lt jaxb bindings xmlns jaxb  http   java sun com xml ns jaxb                 xmlns xsd  http   www w3 org 2001 XMLSchema                 jaxb version  2 0  gt       lt jaxb bindings schemaLocation  YOUR URL wsdl types schema1  gt           lt jaxb schemaBindings gt               lt jaxb package name  your package name schema1   gt           lt  jaxb schemaBindings gt       lt  jaxb bindings gt       lt jaxb bindings schemaLocation  YOUR URL  wsdl types schema2  gt           lt jaxb schemaBindings gt               lt jaxb package name  your package name schema2   gt           lt  jaxb schemaBindings gt       lt  jaxb bindings gt   lt  jaxb bindings gt    The package name can be anything you want it to be  as long as it doesn t contain any reserved keywords in Java  Next you have to create the wsimport bat script to generate your packaged and code at the preferred location   cd C  YOUR PATH TO PLACE THE PACKAGES wsimport -keep -verbose -b  C  YOUR PATH TO schema xjb  YOUR URL wsdl pause     If you do not want to use cd  you can put the wsimport bat in  C  YOUR PATH TO PLACE THE PACKAGES   If you run it without -keep -verbose it will only generate the packages but not the  java files   The -b will make sure the schema xjc is used when generating

[maven-2] How can I tell jaxb / Maven to generate multiple schema packages?

Examples related to maven-2

Examples related to jaxb

Examples related to schema

Examples related to xsd

Examples related to java