How to use a class customization to resolve file generating conflicts

Question

I am trying to use Maven to generate JAXB files to be used by Spring framework, but Maven displays following errors:

I understand that it is unable to generate files with the names, but I am not sure how to resolve the issue. So far, I visited following links. 1, 2, 3

org.xml.sax.SAXParseException; systemId: http://www5v80.elsyarres.net/service.asmx?wsdl; lineNumber: 5; columnNumber: 39; A class/interface with the same name "hello.wsdl.SearchFlights" is already in use. Use a class customization to resolve this conflict.
....
org.xml.sax.SAXParseException; systemId: http://www5v80.elsyarres.net/service.asmx?wsdl; lineNumber: 12; columnNumber: 43; (Relevant to above error) another "SearchFlights" is generated from here.
....
org.xml.sax.SAXParseException; systemId: http://www5v80.elsyarres.net/service.asmx?wsdl; lineNumber: 371; columnNumber: 42; A class/interface with the same name "hello.wsdl.GetFlightDetails" is already in use. Use a class customization to resolve this conflict.
....

Maven plugin

    <plugin>
        <artifactId>maven-war-plugin</artifactId>
        <version>2.4</version>
        <configuration>
            <warSourceDirectory>WebContent</warSourceDirectory>
        </configuration>
    </plugin>
    <plugin>
        <groupId>org.jvnet.jaxb2.maven2</groupId>
        <artifactId>maven-jaxb2-plugin</artifactId>
        <version>0.12.3</version>
        <executions>
            <execution>
                <goals>
                    <goal>generate</goal>
                </goals>
            </execution>
        </executions>
        <configuration>
            <schemaLanguage>WSDL</schemaLanguage>
            <generatePackage>hello.wsdl</generatePackage>
            <schemas>
                <schema>
                    <url>http://www5v80.elsyarres.net/service.asmx?wsdl</url>
                </schema>
            </schemas>
        </configuration>
    </plugin>

I added following package-info.java file to the hello.wsdl package but it did not help.

@XmlSchema( 
    namespace = "ElsyArres.API",
    elementFormDefault = XmlNsForm.QUALIFIED) 
package hello.wsdl;

import javax.xml.bind.annotation.XmlNsForm;
import javax.xml.bind.annotation.XmlSchema;

were you able to fix this issue?? If yes, how? I am also facing similar issue and I dont want to go ahead with `-XautoNameResolution` option. I am interested for binding approach. — Khuzi, Mar 08 '18 at 19:51
for me all I had to do was to remove the package specification — Ahmed Hasn., Jul 05 '22 at 10:50

score 62 · Accepted Answer · edited Sep 28 '22 at 03:06

The error message you are facing basically states that some names in the the typessection of your wsdl are used two times. In your case all <element>tags have the same name as their corresponding types (defined as <complexType>).

Example:

  <s:element name="SearchFlights">
    <s:complexType>
      <s:sequence>
        <s:element minOccurs="0" maxOccurs="1" name="SoapMessage" type="tns:SearchFlights" />
      </s:sequence>
    </s:complexType>
  </s:element>

  <s:complexType name="SearchFlights">
    <s:complexContent mixed="false">
      <s:extension base="tns:SoapMessageBase">
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="1" name="Request" type="tns:SearchFlightsRequest" />
          <s:element minOccurs="0" maxOccurs="1" name="Response" type="tns:SearchFlightsResponse" />
        </s:sequence>
      </s:extension>
    </s:complexContent>
  </s:complexType>

This is quite uncommon.

There are basically two options to resolve these issues:

Use autoNameResolution

 <plugin>
     <groupId>org.jvnet.jaxb2.maven2</groupId>
     <artifactId>maven-jaxb2-plugin</artifactId>
     <version>0.13.1</version>
     <executions>
         <execution>
             <goals>
                 <goal>generate</goal>
             </goals>
         </execution>
     </executions>
     <configuration>

         <args>
             <arg>-XautoNameResolution</arg>
         </args>

         <schemaLanguage>WSDL</schemaLanguage>
         <generatePackage>hello.wsdl</generatePackage>
         <schemas>
             <schema>
                 <url>http://www5v80.elsyarres.net/service.asmx?wsdl</url>
             </schema>
          </schemas>
      </configuration>
  </plugin>

The plugin will resolve all naming conflicts through appending numbers to every colliding name. In the above mentioned case of SearchFlights this will result in SearchFlights and SearchFlights2 being generated.

A better way would be to use a binding file to resolve all name conflicts in advance. Binding files mostly contain XPATHexpression and transformation rules. A binding file that appends to every declarations name is the following:

<?xml version="1.0" encoding="UTF-8"?>
<jaxws:bindings wsdlLocation="http://www5v80.elsyarres.net/service.asmx?wsdl"
            xmlns:jaxws="http://java.sun.com/xml/ns/jaxws"
            xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
            xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" version="2.1"
            xmlns:xs="http://www.w3.org/2001/XMLSchema">

    <jaxws:bindings node="wsdl:definitions/wsdl:types/xs:schema[@targetNamespace='ElsyArres.API']">
        <jaxb:schemaBindings>
            <jaxb:nameXmlTransform>
                <jaxb:elementName suffix="Elem"/>
            </jaxb:nameXmlTransform>
        </jaxb:schemaBindings>
    </jaxws:bindings>
</jaxws:bindings>

There are other options for jaxb:nameXmlTransform like suffixes and prepending to other kind of xml elements (like types).

Sadly i could not get to work this binding file with the org.jvnet.jaxb2.maven2:maven-jaxb2-plugin( but i am sure there is a working configuration)

It nevertheless works with the org.codehaus.mojo:jaxws-maven-plugin and the following configuration.

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>jaxws-maven-plugin</artifactId>
    <version>2.4.1</version>
    <executions>
        <execution>
            <goals>
                <goal>wsimport</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
        <bindingFiles>
         <bindingFile>${basedir}/src/main/resources/bindings.xjb</bindingFile>
        </bindingFiles>
        <wsdlUrls>
            <wsdlUrl>http://www5v80.elsyarres.net/service.asmx?wsdl</wsdlUrl>
        </wsdlUrls>
        <vmArgs>
            <vmArg>-Djavax.xml.accessExternalSchema=all</vmArg>
        </vmArgs>
    </configuration>
</plugin>

I am interested for binding approach. Were you able to get working with `org.jvnet.jaxb2.maven2:maven-jaxb2-plugin` ?? — Khuzi, Mar 08 '18 at 19:52
`-XautoNameResolution` works but now I am getting error `Two declarations cause a collision in the ObjectFactory class.` Any suggestions?? — , Nov 25 '19 at 07:35
I used the -XautoNameResolution solution, and fixed the problem perfectly. Thanks for the solution! spent a day on it. — sen, Feb 04 '22 at 02:17
wsimport -XautoNameResolution does not work (error!) -B-XautoNameResolution does nothing... :\ — marcolopes, Sep 28 '22 at 03:09

score 33 · Answer 2 · answered Sep 20 '17 at 13:33

33

If the autoNameResolution fix

 <args>
     <arg>-XautoNameResolution</arg>
 </args>

doesn't work, try:

 <args>
     <arg>-B-XautoNameResolution</arg>
 </args>

answered Sep 20 '17 at 13:33

trunkc

6,223
4
34
49

1

thanks, this works also with wsimport utility from jdk – francarl Jan 25 '18 at 10:25

Hamid Mohayeji · Answer 3 · 2019-08-13T16:50:30.233

19

Removing <generatePackage></generatePackage> tag solves the problem.

However, the consequence of this removal is that your packages will be created from the xml namespace. For example, the namespace example.com/xyz will result to the package com.example.xyz

edited Aug 13 '19 at 16:50

answered Oct 04 '18 at 11:46

Hamid Mohayeji

3,977
3
43
55

This does seem like the easiest solution. Seems to work for me. I wonder what the drawbacks are. – andrew Feb 09 '19 at 13:12
Exactly, after spending good amount of time able to generate source, would like to know the drawbacks of it. – Delli Kilari Mar 28 '20 at 06:30

thoredge · Answer 4 · 2019-03-27T09:31:57.520

Removing generatePackage as hamid-mohayeji mentions fixes a lot of cases (at least cases where your xsds are sane). The setting tries to put all entities into the same namespace and that's bound to go wrong in non-simple cases. However omitting the package leaves you with packages created from the namespace. For example http://www.co.com/srvc/api/common would become package com.co.srvc.api.common.

This can be remedied by adding a simple binding file. Configure <bindingDirectory>src/main/resources/bindings</bindingDirectory> in the pom and add a binding file something.xjb to the binding directory. Here you need to refer to individual relatively to this file.

This file sets packages for each xsd-file individually:

<?xml version="1.0" encoding="UTF-8"?>
<jaxb:bindings xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" jaxb:version="2.0">

    <jaxb:bindings schemaLocation="../schemas/common.xsd">
        <jaxb:schemaBindings>
            <jaxb:package name="com.mycomp.myapp.co.common" />
        </jaxb:schemaBindings>
    </jaxb:bindings>

    ... more bindings

</jaxb:bindings>

score 4 · Answer 5 · answered Jul 09 '20 at 22:31

I had the same problem for xsd to jaxb and using jaxb2-maven-plugin from org.codehaus.mojo. There was a packageName under configuration creates all the generated files under the same package caused the issue

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>jaxb2-maven-plugin</artifactId>
    <version>1.5</version>
    <executions>
        <execution>
            <goals>
                <goal>xjc</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
        <outputDirectory>target/generated-sources/jaxb</outputDirectory>
        <schemaDirectory>src/main/xsd</schemaDirectory>
        <schemaFiles>test.xsd</schemaFiles>
        <!-- <packageName>com.example.myschema</packageName> -->
    </configuration>
</plugin>

score 3 · Answer 6 · answered Jun 29 '20 at 05:44

When you're using

jaxws-maven-plugin

maven plugin to generate classes from WSDL use below arguments to resolve this issue.

<execution>
 <configuration>
    <xjcArgs>
        <xjcArg>-XautoNameResolution</xjcArg>
    </xjcArgs>
 </configuration>
</execution>

score 3 · Answer 7 · answered Jul 15 '20 at 15:24

3

All the answers above didnt worked...

But this:

<configuration>
  <defaultOptions>
    <autoNameResolution>true</autoNameResolution>
  </defaultOptions>
</configuration>

answered Jul 15 '20 at 15:24

Mert Aksoy

372
1
4
12

score 1 · Answer 8 · answered Feb 03 '21 at 13:43

1

 <defaultOptions>
        <autoNameResolution>true</autoNameResolution>
</defaultOptions>

This worked for me for Apache CXF Plugin.

answered Feb 03 '21 at 13:43

Sushma Kamavaram Ellur

46
1

How to use a class customization to resolve file generating conflicts

8 Answers8

Linked