The jaxb binding file is really the only way, but they can be very tricky to get right. Can you post a sample project with a stripped down wsdl or something?
Dan On Tuesday, November 22, 2011 11:07:59 AM David Brown wrote: > Hello cxfers, I have the dubious task of consuming a .NET 2.0 generated > WSDL using our internally developed SOAP client. The .NET WS is public > and we have no control over the generation of the WSDL. > > Therefore, we must have a solution in the binding or the WSDL itself. > > I am currently running the wsdl2java against the WSDL as a file protocol > instead of HTTP. > > The invoking commandline follows: > > ~/dev/apache-cxf-2.5.0/bin/wsdl2java -autoNameResolution -compile > -client -d . -p com.sexingtechnologies.TestWS -frontend jaxws21 > TestWS/TestWS.wsdl > > The error condition returned is as follows: > > WSDLToJava Error: Thrown by JAXB: > Thrown by JAXB: > Property "Any" is already defined. Use <jaxb:property> to resolve this > conflict. > > ****************************************************************** > > I have tried all of the jaxb binding and xsd tricks I could find on > Google to change the element attribute name (any) to something other but > this to date has not worked. > > ****************************************************************** > > Using the service-repository.com SOAP client: > > http://www.service-repository.com/client/start > > the target WSDL functions perfectly. > > So, there must be some on-the-fly trick way of making errant WSDLs > behave. > > Any suggestions rants or raves welcomed. > > Please advise, David. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
