You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by MK <sp...@gmail.com> on 2013/01/14 16:16:54 UTC
Re: TESTCASE: ObjectFactory and Multiple WSDLs in same namespace
Daniel,
how I can improve WS server side avoiding this situation? No I getting the
same problem with my WS. When I providing wsdls to others developers, they
generating wsdl2java get conflicts based on this thread problems.
--
View this message in context: http://cxf.547215.n5.nabble.com/ObjectFactory-and-Multiple-WSDLs-in-same-namespace-tp5717528p5721555.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: TESTCASE: ObjectFactory and Multiple WSDLs in same namespace
Posted by Daniel Kulp <dk...@apache.org>.
On Jan 14, 2013, at 10:16 AM, MK <sp...@gmail.com> wrote:
> Daniel,
>
> how I can improve WS server side avoiding this situation? No I getting the
> same problem with my WS. When I providing wsdls to others developers, they
> generating wsdl2java get conflicts based on this thread problems.
The best option is to make sure ALL the objects in the package pretty much get included in the schemas for all the WSDL's, even if they aren't used in a particular WSDL. You can do that with @XmlSeeAlso annotations all over the place to make sure all the objects get included. You can also add a"jaxb.index" file into the package that is a simple list of simple class names in that package. That should be picked up by JAXB and then all those types included.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com