On Apr 23, 2013, at 11:44 PM, kurt-apache-cxf <[email protected]> wrote:
> Ok, that worked. > > I created a folder and changed all of the schemaLocation="http:.* lines to a > relative path (with folder). > > wsdl2java output 11k lines of problems. The line/column values of the > offending duplicate are still blank but each entry does point to the > line/column where the first one is. Lots more to go on than I had before. > > Still need a few pointers on what to do in a binding file to fix this. Will > start a new thread. You can TRY passing the -autoNameResolution flag to wsdl2java. That can resolve a lot of these things automatically. Not all of them, but it might cut down the work a little. Dan > > On 4/23/2013 8:02 PM, Freeman Fang wrote: >> Hi, >> >> You can just run wsdl2java against local wsdls, using relative path should >> work >> －－－－－－－－－－－－－ >> Freeman(Yue) Fang >> >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Web: http://fusesource.com | http://www.redhat.com/ >> Twitter: freemanfang >> Blog: http://freemanfang.blogspot.com >> http://blog.sina.com.cn/u/1473905042 >> weibo: @Freeman小屋 >> >> On 2013-4-24, at 上午10:23, kurt-apache-cxf wrote: >> >>> I have them stored locally and have added newlines. Is there an easy to >>> get wsdl2java to read the WSDL and XSDs from disk rather than the server? >>> I took a couple of runs at it before posting in the forum and couldn't make >>> it work. >>> >>> On 4/23/2013 3:01 PM, Jason Pell wrote: >>>> Can you format the xsd locally to add newlines? At least it might provide >>>> more info >>>> >>>> Can you run it through an xsd validator perhaps a web one. >>>> >>>> I would not recommended the eclipse one as you will probably crash eclipse. >>>> >>>> Sent from my Galaxy S2 >>>> On Apr 24, 2013 3:06 AM, "kurt-apache-cxf" < >>>> [email protected]> wrote: >>>> >>>>> I'm trying to create a CXF client for a web service over which I have no >>>>> control. The related/problematic XSD is 210KB in size. Looks to have been >>>>> created using a dotNet wizard that converted an entire db schema/DDL. >>>>> >>>>> Here is the wsdl2java output: >>>>> >>>>> <code> >>>>> wsdl2java - Apache CXF 2.5.10 >>>>> >>>>> WSDLToJava Error: Thrown by JAXB: >>>>> Thrown by JAXB: >>>>> Thrown by JAXB: Two declarations cause a collision in the ObjectFactory >>>>> class. >>>>> >>>>> Thrown by JAXB: (Related to above error) This is the other declaration. >>>>> >>>>> >>>>> org.apache.cxf.tools.common.**ToolException: Thrown by JAXB: >>>>> Thrown by JAXB: >>>>> Thrown by JAXB: Two declarations cause a collision in the ObjectFactory >>>>> class. >>>>> >>>>> Thrown by JAXB: (Related to above error) This is the other declaration. >>>>> >>>>> at org.apache.cxf.tools.wsdlto.**databinding.jaxb.** >>>>> JAXBBindErrorListener.th<http://org.apache.cxf.tools.wsdlto.databinding.jaxb.JAXBBindErrorListener.th> >>>>> rowError(**JAXBBindErrorListener.java:40) >>>>> ... >>>>> </code> >>>>> >>>>> I've downloaded the XSD to disk and opened it. There are no newlines in >>>>> the doc. I'm guessing this is causing an overload in the Apache CXF code >>>>> that points to the line/cloumn where the problem is. >>>>> >>>>> I'd post the WSDL/XSD but the web service isn't public and would get me >>>>> into trouble with a customer. >>>>> >>>>> I've tried running version 2.2.6, 2.5.20, 2.6.7 and 2.7.4 and all have a >>>>> similar issue. autoNameResolution has no effect. The XSD is huge, a look >>>>> through it with some diagnostic xpath isn't revealing where the problem >>>>> is. >>>>> I'm clueless as to what I should add as custom bindings. >>>>> >>>>> Any pointers as to how to resolve? >>>>> >>>>> >> > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
