JAXB error on wsdl2java ....

[Xiangmin Li <xi...@landslide.com>]

I would like to get some help on resolving the following error when I
used the CXF wsdl2java to generate the client side code:

 

C:\java\ApacheCXF\bin>wsdl2java -p cxf.client.salesforce -client -d
C:\temp\cxf\salesforce C:\SalesForce\wsdl\Axis2_enterprise.wsdl

WSDLToJava Error : Thrown by JAXB : A class/interface with the same name
"cxf.client.salesforce.DescribeLayout" is already in use. Use a class
customization to resolve this conflict.

 

If I directly use an XSD file to generate the schema Java objects with
JAXB for XML data binding, I know I can add certain customizations to
the XSD to resolve this kind of errors. With a WSDL instead of an XSD, I
am not sure what I should do with it to resolve this error. Usually this
kind of errors is caused by the underscore character or/and the
upper/lower cases of letters. In this case, the WSDL does have both
"DescribeLayout" and "describeLayout" defined as different elements.

 

Thanks for the help.

Re: JAXB error on wsdl2java ....

[Daniel Kulp <dk...@apache.org>]

It's pretty much exactly the same as if you used the jaxb customizations 
with the jaxb xjc tool.    wsdl2java has a -b flag that can be used to 
specify and external jaxb binding file.   Or, you can put the jaxb 
customizations directly into the schema sections of the wsdl.  

Dan

On Wednesday 17 October 2007, Xiangmin Li wrote:
> I would like to get some help on resolving the following error when I
> used the CXF wsdl2java to generate the client side code:
>
>
>
> C:\java\ApacheCXF\bin>wsdl2java -p cxf.client.salesforce -client -d
> C:\temp\cxf\salesforce C:\SalesForce\wsdl\Axis2_enterprise.wsdl
>
> WSDLToJava Error : Thrown by JAXB : A class/interface with the same
> name "cxf.client.salesforce.DescribeLayout" is already in use. Use a
> class customization to resolve this conflict.
>
>
>
> If I directly use an XSD file to generate the schema Java objects with
> JAXB for XML data binding, I know I can add certain customizations to
> the XSD to resolve this kind of errors. With a WSDL instead of an XSD,
> I am not sure what I should do with it to resolve this error. Usually
> this kind of errors is caused by the underscore character or/and the
> upper/lower cases of letters. In this case, the WSDL does have both
> "DescribeLayout" and "describeLayout" defined as different elements.
>
>
>
> Thanks for the help.



-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727    C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog