We ran into this at one point with CXF as well in the ws-rm module. I think the only way we got around it was to fully specify the package name for the entire schema *AND* specify the parse methods we need for the specific adapters:
Example: http://svn.apache.org/repos/asf/cxf/trunk/rt/ws/rm/src/main/resources/schemas/wsdl/wsrm-1.1.xjb That said, that was a long time ago. Not sure if ALL of that is still needed. Dan On Sep 4, 2012, at 7:28 AM, djed-pfeiler <[email protected]> wrote: > Ok .. we have the problem. > We generate different WSDLs and therefore have mutliple Adapter-Classes in > THE SAME PACKAGES in the JAR files! > Due to classloading we get the Adapter1.class from wsi-XX1-cxf-services-1.0 > or from wsi-XX2-cxf-services-1.0. > JAXB-custombindings are different in Projekt XX1 and XX2. > > *How* can we tell CXF to generate the adapter classes to different packages > .. not always to org.w3._2001.xmlschema ? > > THX! > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/xsd-date-becomes-xsd-dateTime-tp5713485p5713533.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
