Just as a quick addition to Jerome's e-mail, I have seen similar anomalies in the wsdl2java when I import other xsd files into my wsdl file. For now I have decided to not to use wsdl2java and rely on Axiom to parse the xml messages, manually, until the wsdl2java is enhanced to handle complex wsdl files with includes and imports.
Gul -----Original Message----- From: Magnet, Jerome (CAR:QT11) Sent: Tuesday, October 17, 2006 5:48 PM To: [email protected] Subject: RE: Compilation error with WSDL2Java and XmlBeans I finally managed to generate something based on the WSDL2Java and the XmlBeans databinding. I have been simplifying my set of xml files (WSDL & XSD) up to a point where the generation provides the set of expected Java files and associated resources. I capture in this long (too long) thread two sets of WSDL files and their WSDL2Java invokation cmds: Set#1: one WSDL file (MyService2.wsdl with WSDL2Java invoke script: wsdl2.bat) with all interface definitions (WSDL/XSD) This one is working - I did not check in depth the generated Java files. But, after a quick tour it seems fine. Set#2: three WSDL files (other ones) This one is just a simple split of the one in set#1. It is simply a cascading pattern of wsdl:include with file1 into file2 into file3. And, that is enough to brake the generation of all XmlBeans derived artifacts. So, it seems clear that WSDL2Java has some issues with wsdl:include. I don't understand how it interferes with the XmlBeans code generation. Also, here is a list of other definition styles that I though were issues with axis2 WSDL2Java (but seems ok to me): - I have two operations in my interface (portType). And, that is not an issue here (Brenan you may want to have a look at that) - I have two different namespaces. One for all WSDL definitions and another for all Schema definitions - I have two parts for the soap binding of the two operations; one part for the SOAP header (header schema element in my namespace) One part for the SOAP body (payload schema element specific to the operation message) That works well and the signature of my operations in my Java interface looks fine (in the working set#1 :) ) So, I think we can close this long email thread. I will submit a JIRA with the attached files. I appreciate all the help I received for this request. This forum is very active. I hope the response from axis2 team will be the same! Final note about what I am trying to do with Axis2. I am currently the editor of the MTOSI XML (WSDL/XSD) solution set, which is an interface developed by Telecom standard organization (www.tmforum.org). I am interested in Axis2 as an open source toolkit to help with the definition of our specifications reference implementation development. Our XML solution set proposes WS based on a set of WSDL and XSD files with a complex level of references. Definitions using import and includes in XSD and WSDL are commonly found across several namespaces (XSD and WSDL) in various locations. The reason for all of that complexity is due to a logical break down of the overal XML definitions from various packages with UML modeling of the interfaces and the data model. So, I will be happy in helping axis2 developers improve the WSDL2Java tool, by testing it against our XML specs. Thanks, Jerome -----Original Message----- From: Spies, Brennan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 1:54 PM To: [email protected] Subject: RE: Compilation error with WSDL2Java and XmlBeans Jerome, I am using the more boilerplate version of <wsdl:binding>, like so... <wsdl:binding> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"; /> <wsdl:operation name="..."> <soap:operation soapAction="..."/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> <wsdl:output> <soap:body use="literal"/> </wsdl:output> ... </wsdl:operation> </wsdl:binding> I've had no problems using the same top-down code generation scenario with XMLBeans. My guess (and it's only a guess) is that the code generator is not handling multiple operations. My advice (which you can take or leave...): 1. File a JIRA. The Axis 2 team has been really good about fixing these. Most of the ones I've filed have been fixed in 24 hrs. or less. 2. If you're pressed for time, change it so that each <portType> and <binding> only has one operation. 3. The namespace should be a URI. I personally prefer URNs myself (never liked URLs for this, seems silly to have protocol info like http:// in a namespace). Something like "urn:tmf854:v1:ws" works... 4. Get rid of the redundant <include>'s on your XSD (e.g. where A is included in B, A is included in C, and B and C are both included in your WSDL). Technically, the code generator should handle it by unique schemaLocation, but it may not be (I suspect this is why you were getting the messages saying it would not overwrite an existing class). Brennan Spies Sr. Programmer Analyst Shared Application Services -----Original Message----- From: Jerome Magnet [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 10:19 AM To: [email protected] Subject: RE: Compilation error with WSDL2Java and XmlBeans Yes. It is definitely WSDL 1.1. Refer to the two nms in all the wsdl;definitions of my wsdl files are based on WSDL 1.1 nms: xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; and xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; We have a lot of tools already making use of these WSDL files. XMLspy is my XML editor (use it with Eclipse plug-ins or native). Also, other tools/middleware such as Artix from IONA can process these WSDL files without any problems. Here are my comments on the two issues found so far: BP2803 I guess this is just a warning. Because it is a valid URI. I also changed that to a true HTTP address in my simplification attempt. BP2105 I moved the wsdl:import above the wsdl:types and the the schema import. It still fails. I don't know how the above issues relate to the issue of not having any XmlBeans Java classes generated for my schema. Should I be expecting that, or should I re-use the Java code I generate for my XSD's using XmlBeans (scomp)? Is there a document that describes the integration process of XmlBeans as databinder with axis2 based on simple example (one operation)? Thanks again, Jerome -----Original Message----- From: Spies, Brennan [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 12:35 PM To: [email protected] Subject: RE: Compilation error with WSDL2Java and XmlBeans It's not WSDL 2.0, or there would be no <portType>, but rather an <interface> definition. The <wsdl:binding> section here does deviate from the standard boilerplate for a sync operation SOAP over HTTP (not using soap:operation and specifying soap:header info, having multiple operations per portType/binding), but it is legal WSDL. From the 1.1 spec (section 3.2): <definitions .... > <binding .... > <soap:binding style="rpc|document" transport="uri"> <operation .... > <soap:operation soapAction="uri"? style="rpc|document"?>? <input> <soap:body parts="nmtokens"? use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?> <soap:header message="qname" part="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?>* <soap:headerfault message="qname" part="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?/>* <soap:header> </input> <output> <soap:body parts="nmtokens"? use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?> <soap:header message="qname" part="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?>* <soap:headerfault message="qname" part="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?/>* <soap:header> </output> <fault>* <soap:fault name="nmtoken" use="literal|encoded" encodingStyle="uri-list"? namespace="uri"?> </fault> </operation> </binding> <port .... > <soap:address location="uri"/> </port> </definitions> It's not shown above, but section 2.4 & 2.5 puts a * after <operation> subelements, showing that multiple operations are allowed. Brennan Spies Sr. Programmer Analyst Shared Application Services -----Original Message----- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 17, 2006 7:20 AM To: [email protected] Subject: Re: Compilation error with WSDL2Java and XmlBeans This looks like WSDL 2.0 , though I'm not sure since I've never used it. Looking at the structure it seems to be. I don't see the style definition for example. Furthermore, you are getting warnings using eclipses WTP validation, the second seeming more important: 1 WS-I: (BP2803) The wsdl:import element's "namespace" attribute value is a relative URI. NotificationService.wsdl 1 WS-I: (BP2105) A wsdl:import element in the WSDL namespace under the wsdl:definitions element, is preceded by child elements other than wsdl:documentation elements. NotificationService.wsdl The error I get running wsdl2java on these is that it can't resolve your binding: [java] 17/10/2006 11:11:01 org.apache.axis2.description.WSDL11ToAxisServiceBuilder findBinding [java] INFO: A service element was not found - picking a random binding! [java] Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGeneration Engin e.java:112) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: org.apache.axis2.AxisFault: No bindings found in wsdl; nested exception is: [java] org.apache.axis2.AxisFault: No bindings found in wsdl [java] at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService( WSDL1 1ToAxisServiceBuilder.java:246) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGeneration Engin e.java:103) [java] ... 2 more HTH, Robert On 10/16/06, Jerome Magnet <[EMAIL PROTECTED]> wrote: > That's the nightly package I used to get the output mentioned earlier > (see below). Also, I tried to simplify the XSD of the messages by > having all definitions in one XSD file. I simplified the message > schema with a simple element definition with one level of element's > containment for each message. And, I have one namespace for WSDL and > XSD definitions. Unfortunately, the result is still the same. I don't > get any XmlBeans Java classes for all schema definitions as I would > get by compiling with XmlBeans. I attached the BAT file (replaced > extension by txt) I use to invoke WSDL2Java. > > Jerome > > >>>> Output based on simplified XSD > Using AXIS2_HOME: D:\Apps\axis2 > Using JAVA_HOME: D:\Java\jdk1.5.0_02 > AXIS2_CLASS_PATH > D:\Apps\axis2;D:\Apps\axis2\lib\activation-1.1.jar;D:\Apps\axis2\lib\a > nn > ogen-0.1.0. > jar;D:\Apps\axis2\lib\axiom-api.jar;D:\Apps\axis2\lib\axiom-dom.jar;D:\A > pps\axis2\lib\axiom-impl.jar > ;D:\Apps\axis2\lib\axis2-adb-1.1-SNAPSHOT.jar;D:\Apps\axis2\lib\axis2-ad > b-codegen-1.1.jar;D:\Apps\ax > is2\lib\axis2-codegen-1.1.jar;D:\Apps\axis2\lib\axis2-java2wsdl-1.1.jar; > D:\Apps\axis2\lib\axis2-jaxb > ri-1.1.jar;D:\Apps\axis2\lib\axis2-jibx-1.1.jar;D:\Apps\axis2\lib\axis2- > kernel-1.1.jar;D:\Apps\axis2 > \lib\axis2-saaj-1.1.jar;D:\Apps\axis2\lib\axis2-spring-1.1.jar;D:\Apps\a > xis2\lib\axis2-tools-1.1.jar > ;D:\Apps\axis2\lib\axis2-xmlbeans-1.1.jar;D:\Apps\axis2\lib\backport-uti > l-concurrent-2.2.jar;D:\Apps > \axis2\lib\commons-codec-1.3.jar;D:\Apps\axis2\lib\commons-fileupload-1. > 1.1.jar;D:\Apps\axis2\lib\co > mmons-httpclient-3.0.1.jar;D:\Apps\axis2\lib\commons-logging-1.1.jar;D:\ > Apps\axis2\lib\geronimo-spec > -jms-1.1-rc4.jar;D:\Apps\axis2\lib\jakarta-httpcore-4.0-alpha2.jar;D:\Ap > ps\axis2\lib\jaxen-1.1-beta- > 10.jar;D:\Apps\axis2\lib\jaxme2-0.5.1.jar;D:\Apps\axis2\lib\jaxmeapi-0.5 > .1.jar;D:\Apps\axis2\lib\jax > mejs-0.5.1.jar;D:\Apps\axis2\lib\jaxmexs-0.5.1.jar;D:\Apps\axis2\lib\jib > x-bind.jar;D:\Apps\axis2\lib > \jibx-run.jar;D:\Apps\axis2\lib\mail-1.4.jar;D:\Apps\axis2\lib\neethi.ja > r;D:\Apps\axis2\lib\servleta > pi-2.3.jar;D:\Apps\axis2\lib\spring-beans-1.2.8.jar;D:\Apps\axis2\lib\sp > ring-context-1.2.8.jar;D:\Ap > ps\axis2\lib\spring-core-1.2.8.jar;D:\Apps\axis2\lib\spring-web-1.2.8.ja > r;D:\Apps\axis2\lib\stax-api > -1.0.1.jar;D:\Apps\axis2\lib\stax-utils-20060915.jar;D:\Apps\axis2\lib\w > oden-1.0.0M6.jar;D:\Apps\axi > s2\lib\wsdl4j-1.6.1.jar;D:\Apps\axis2\lib\wstx-asl-3.0.1.jar;D:\Apps\axi > s2\lib\xbean-2.2.0.jar;D:\Ap > ps\axis2\lib\xercesImpl-2.8.1.jar;D:\Apps\axis2\lib\xml-apis-1.3.03.jar; > D:\Apps\axis2\lib\XmlSchema. > jar > Retrieving document at 'NotificationServiceSOAP.wsdl', relative to > 'file:/D:/Jeromem/Code/testAxis2/ ./wsdl/'. > Retrieving document at 'NotificationService.wsdl', relative to > 'file:/D:/Jeromem/Code/testAxis2/wsdl > /NotificationServiceSOAP.wsdl'. > Retrieving schema at 'xsd/NotificationService2.xsd', relative to > 'file:/D:/Jeromem/Code/testAxis2/ws > dl/NotificationService.wsdl'. > Retrieving document at 'Exceptions.wsdl', relative to > 'file:/D:/Jeromem/Code/testAxis2/wsdl/Notifica > tionService.wsdl'. > Retrieving schema at 'xsd/Exceptions2.xsd', relative to > 'file:/D:/Jeromem/Code/testAxis2/wsdl/Except > ions.wsdl'. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File > src\src\org\tmforum\mtosi\ws\NotificationServiceSkeletonInterface.java > will not be overwr > itten. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File src\src\org\tmforum\mtosi\ws\NotificationServiceSkeleton.java > will not be overwritten. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File > src\src\org\tmforum\mtosi\ws\NotificationServiceMessageReceiverInOut.jav > a will not be ove > rwritten. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File > src\src\org\tmforum\mtosi\ws\ProcessingFailureExceptionException.java > will not be overwri > tten. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File src\src\org\tmforum\mtosi\ws\NotificationService.java will > not be overwritten. Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File > src\src\org\tmforum\mtosi\ws\ProcessingFailureExceptionException.java > will not be overwri > tten. > Oct 16, 2006 9:37:10 PM org.apache.axis2.wsdl.codegen.writer.ClassWriter > createOutFile > INFO: File src\src\org\tmforum\mtosi\ws\NotificationServiceStub.java > will not be overwritten. > > -----Original Message----- > From: robert lazarski [mailto:[EMAIL PROTECTED] > Sent: Monday, October 16, 2006 8:53 PM > To: [email protected] > Subject: Re: Compilation error with WSDL2Java and XmlBeans > > > This zip file has all the jars you need - only these jars should be in > your classpath. > > http://people.apache.org/dist/axis2/nightly/axis2-std-1.1-SNAPSHOT-bin > .z > ip > > Could you try that packages jars and let us know if that works for > you? If not I'll try and give a look at it. > > Robert > > On 10/16/06, Jerome Magnet <[EMAIL PROTECTED]> wrote: > > First, thanks for your quick replies. > > > > Now, I used in my classpath all the nightly jars from the > > "%AXIS2_HOME%\lib\*.jar" as defined in the WSDL2Java.bat (or sh). I > > am > > > not sure what you mean by std-bin? I looked at the min bin nightly > > package. But, it does not have the codegen libraries (WSDL2Java > > class not found). > > > > I will try to send all my WSDL/XSD files in this email. I tried in a > > zip file and changing the zip by txt but it seems that posting to > > this > > > mailing list always fails with a zip formated file. Note that all > > xsd files are in xsd folder found with wsdl files. > > > > Jerome > > > > -----Original Message----- > > From: robert lazarski [mailto:[EMAIL PROTECTED] > > Sent: Monday, October 16, 2006 5:06 PM > > To: [email protected] > > Subject: Re: Compilation error with WSDL2Java and XmlBeans > > > > > > I also just noticed you have some old jars in your classpath. Try > > placing _only_ the jars in your classpath that are from the nightly > > std-bin distro. > > > > Robert > > > > On 10/16/06, robert lazarski <[EMAIL PROTECTED]> wrote: > > > Post your wsdl and schemas and maybe we can help. The wsdl does > > > validate, right ? > > > > > > Robert > > > > > > On 10/16/06, Jerome Magnet <[EMAIL PROTECTED]> wrote: > > > > Robert, > > > > > > > > I tried the latest nightly load. It does not fail as before. > > > > But, I got the following output (see below): > > > > > > > > I got three java classes and 2 XML resources. > > > > I don't see any XMLBeans Java classes based on the XML schema of > > > > all > > > > > > messages (request/Response/Exception). Also, reading the > > > > generated > > > > > wsdl it has all the message schema missing. Actually, the > > > > namespace is missing. And, the prefix of my parts are "null" > > > > (See extract below)? Does it mean that I can use the Java > > > > classes compiled with XmlBeans? Is there a recipe to follow on > > > > how to integrate XmlBeans library of java classes with the Java > > > > code generated by axis2? > > > > > > > > Thanks, > > > > > > > > Jerome > > > > > > > > >>> generated WSDL > > > > <wsdl:definitions > > > > xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; > > > > xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; > > > > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"; > > > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > > > xmlns:tmf854WS="tmf854.v1.ws" > > > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > > > targetNamespace="tmf854.v1.ws"> > > > > <wsdl:types/> > > > > <wsdl:message name="subscribe"> > > > > <wsdl:part name="part1" element="null:subscribe"/> > > > > </wsdl:message> > > > > <wsdl:message name="subscribe"> > > > > <wsdl:part name="mtosiHeader" element="null:header"/> > > > > </wsdl:message> > > > > <wsdl:message name="subscribeResponse"> > > > > <wsdl:part name="part1" element="null:subscribeResponse"/> > > > > </wsdl:message> > > > > <wsdl:message name="subscribeResponse"> > > > > <wsdl:part name="mtosiHeader" element="null:header"/> > > > > </wsdl:message> > > > > <wsdl:message name="ProcessingFailureException"> > > > > <wsdl:part name="part1" > > > > element="null:ProcessingFailureException"/> > > > > ... > > > > > > > > >>> output from WSDL2Java > > > > Retrieving document at 'NotificationServiceSOAP.wsdl', relative > > > > to > > > > > 'file:/D:/Jeromem/Code/testAxis2/ ./wsdl/'. Retrieving document > > > > at > > > > > 'NotificationService.wsdl', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl > > > > /NotificationServiceSOAP.wsdl'. > > > > Retrieving schema at 'xsd/interfaces/NotificationService.xsd', > > relative > > > > to 'file:/D:/Jeromem/Code/te > > > > stAxis2/wsdl/NotificationService.wsdl'. > > > > Retrieving schema at '../common/Header.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i > > > > nterfaces/NotificationService.xsd'. > > > > Retrieving schema at 'HeaderVendorExtensions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl > > > > /xsd/common/Header.xsd'. > > > > Retrieving schema at 'Definitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/common > > > > /HeaderVendorExtensions.xsd'. > > > > Retrieving schema at '../networkResources/Notifications.xsd', > > relative > > > > to 'file:/D:/Jeromem/Code/tes > > > > tAxis2/wsdl/xsd/interfaces/NotificationService.xsd'. > > > > Retrieving schema at 'GlobalDefinitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/ > > > > networkResources/Notifications.xsd'. > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/ > > > > xsd/networkResources/GlobalDefinitions.xsd'. > > > > Retrieving schema at 'VendorExtensions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/n > > > > etworkResources/Notifications.xsd'. > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/ > > > > xsd/networkResources/VendorExtensions.xsd'. > > > > Retrieving schema at 'LayerRates.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/network > > > > Resources/Notifications.xsd'. > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/ > > > > xsd/networkResources/LayerRates.xsd'. > > > > Retrieving schema at 'ProbableCauses.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/net > > > > workResources/Notifications.xsd'. > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/ > > > > xsd/networkResources/ProbableCauses.xsd'. > > > > Retrieving document at 'Exceptions.wsdl', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/Notifica > > > > tionService.wsdl'. > > > > Retrieving schema at 'xsd/interfaces/Exceptions.xsd', relative > > > > to 'file:/D:/Jeromem/Code/testAxis2/w > > > > sdl/Exceptions.wsdl'. > > > > Retrieving schema at '../common/Header.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i > > > > nterfaces/Exceptions.xsd'. > > > > Retrieving schema at 'VendorExtensions.xsd', relative to > > > > 'file:/D:/Jeromem/Code/testAxis2/wsdl/xsd/i > > > > nterfaces/Exceptions.xsd'. > > > > Oct 16, 2006 4:05:33 PM > > org.apache.axis2.wsdl.codegen.writer.ClassWriter > > > > createOutFile > > > > INFO: File > > src\src\org\tmforum\mtosi\ws\NotificationServiceSkeleton.java > > > > will not be overwritten. > > > > Oct 16, 2006 4:05:33 PM > > org.apache.axis2.wsdl.codegen.writer.ClassWriter > > > > createOutFile > > > > INFO: File > > > > > > src\src\org\tmforum\mtosi\ws\NotificationServiceMessageReceiverInOut > > .j > > av > > > > a will not be ove > > > > rwritten. > > > > Oct 16, 2006 4:05:33 PM > > org.apache.axis2.wsdl.codegen.writer.ClassWriter > > > > createOutFile > > > > INFO: File > > > > > > src\src\org\tmforum\mtosi\ws\ProcessingFailureExceptionException.jav > > a > > > > will not be overwri > > > > tten. > > > > > > > > -----Original Message----- > > > > From: robert lazarski [mailto:[EMAIL PROTECTED] > > > > Sent: Saturday, October 14, 2006 6:51 PM > > > > To: [email protected] > > > > Subject: Re: Compilation error with WSDL2Java and XmlBeans > > > > > > > > > > > > Have you tried the latest nightly ? > > > > > > > > http://people.apache.org/dist/axis2/nightly/axis2-1.1-SNAPSHOT.w > > > > ar > > > > http://people.apache.org/dist/axis2/nightly/axis2-std-1.1-SNAPSHOT > > > > -b > > > > in.z > > > > ip > > > > > > > > If the problem persists, please create a jira and upload your > > > > wsdl > > > > > and schemas. > > > > > > > > HTH, > > > > Robert > > > > > > > > On 10/14/06, Jerome Magnet <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > I have the following error with WSDL2Java (see below). I don't > > > > > understand what is the issue. The WSDL/XSD validates with > > > > > XMLSpy. Also, I can compile all XSD with XmlBeans (scomp). It > > > > > seems that the issue is in: NotificationService.xsd:29:40 And, > > > > > there is a reference to a null element in the namespace? The > > > > > line numbers refer to a simpletype string with enumerations. > > > > > > > > > > Finally, I noticed some issues with wsdl:import. It went away > > > > > when > > > > > > > I put all my WSDL files in the same folder. > > > > > > > > > > Thanks, > > > > > Jerome > > > > > > > > > > >>> Compilation output with WSDL2Java > > > > > Using AXIS2_HOME: D:\Apps\axis2 > > > > > Using JAVA_HOME: D:\Java\jdk1.5.0_02 > > > > > AXIS2_CLASS_PATH > > > > > D:\Apps\axis2;D:\Apps\xmlbeans-2.1.0\lib\jsr173_1.0_api.jar;D: > > > > > \A > > > > > pp > > > > > s\xm > > > > > lbeans-2.1.0\ > > > > > > > > > lib\resolver.jar;D:\Apps\axis2\lib\annogen-0.1.0.jar;D:\Apps\axi > > > > s2 > > > > \l > > > > ib\a > > > > xiom-api-1.0.jar;D:\Apps\axi > > > > > > > > > s2\lib\axiom-dom-1.0.jar;D:\Apps\axis2\lib\axiom-impl-1.0.jar;D: > > > > \A > > > > pp > > > > s\ax > > > > is2\lib\axis2-adb-1.0.jar;D: > > > > > > > > > \Apps\axis2\lib\axis2-codegen-1.0.jar;D:\Apps\axis2\lib\axis2-ji > > > > bx > > > > -1 > > > > .0.j > > > > ar;D:\Apps\axis2\lib\axis2-k > > > > > > > > > ernel-1.0.jar;D:\Apps\axis2\lib\axis2-tools-1.0.jar;D:\Apps\axis > > > > 2\ > > > > li > > > > b\ax > > > > is2-xmlbeans-1.0.jar;D:\Apps > > > > > > > > > \axis2\lib\backport-util-concurrent-2.1.jar;D:\Apps\axis2\lib\co > > > > mm > > > > on > > > > s-co > > > > dec-1.3.jar;D:\Apps\axis2\li > > > > > > > > > b\commons-fileupload-1.0.jar;D:\Apps\axis2\lib\commons-httpclien > > > > t- > > > > 3. > > > > 0.ja > > > > r;D:\Apps\axis2\lib\commons- > > > > > > > > > logging-1.0.4.jar;D:\Apps\axis2\lib\geronimo-spec-activation-1.0 > > > > .2 > > > > -r > > > > c4.j > > > > ar;D:\Apps\axis2\lib\geronim > > > > > > > > > o-spec-javamail-1.3.1-rc5.jar;D:\Apps\axis2\lib\geronimo-spec-jm > > > > s- > > > > 1. > > > > 1-rc > > > > 4.jar;D:\Apps\axis2\lib\jaxe > > > > > > > > > n-1.1-beta-8.jar;D:\Apps\axis2\lib\jaxme2-0.5.1.jar;D:\Apps\axis > > > > 2\ > > > > li > > > > b\ja > > > > xmeapi-0.5.1.jar;D:\Apps\axi > > > > > > > > > s2\lib\jaxmejs-0.5.1.jar;D:\Apps\axis2\lib\jaxmexs-0.5.1.jar;D:\ > > > > Ap > > > > ps > > > > \axi > > > > s2\lib\log4j-1.2.13.jar;D:\A > > > > > > > > > pps\axis2\lib\neethi-1.0.1.jar;D:\Apps\axis2\lib\servletapi-2.3. > > > > ja > > > > r; > > > > D:\A > > > > pps\axis2\lib\stax-api-1.0.j > > > > > > > > > ar;D:\Apps\axis2\lib\stax-utils-20060501.jar;D:\Apps\axis2\lib\w > > > > sd > > > > l4 > > > > j-1. > > > > 5.2.jar;D:\Apps\axis2\lib\ws > > > > > > > > > tx-asl-2.9.3.jar;D:\Apps\axis2\lib\xbean-2.1.0.jar;D:\Apps\axis2 > > > > \l > > > > ib > > > > \Xml > > > > Schema-1.0.2.jar > > > > > Retrieving document at 'NotificationServiceSOAP.wsdl', > > > > > relative to > > > > > > > 'file:/D:/Jeromem/Code/axis2/./ws dl/'. Retrieving document at > > > > > 'NotificationService.wsdl', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/Not > > > > > > > > > > ificationServiceSOAP.wsdl'. > > > > > Retrieving schema at 'xsd/interfaces/NotificationService.xsd', > > > > > relative to 'file:/D:/Jeromem/Code/ax > > > > > is2/wsdl/NotificationService.wsdl'. > > > > > > > > > > Retrieving schema at '../common/Header.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/inter > > > > > faces/NotificationService.xsd'. > > > > > Retrieving schema at 'HeaderVendorExtensions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd > > > > > /common/Header.xsd'. > > > > > Retrieving schema at 'Definitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/common/Hea > > > > > derVendorExtensions.xsd'. > > > > > Retrieving schema at '../networkResources/Notifications.xsd', > > > > > relative to 'file:/D:/Jeromem/Code/axi > > > > > s2/wsdl/xsd/interfaces/NotificationService.xsd'. > > > > > > > > > > Retrieving schema at 'GlobalDefinitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/netw > > > > > orkResources/Notifications.xsd'. > > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/ > > > > > networkResources/GlobalDefinitions.xsd'. > > > > > Retrieving schema at 'VendorExtensions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/netwo > > > > > rkResources/Notifications.xsd'. > > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/ > > > > > networkResources/VendorExtensions.xsd'. > > > > > Retrieving schema at 'LayerRates.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/networkReso > > > > > urces/Notifications.xsd'. > > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/ > > > > > networkResources/LayerRates.xsd'. > > > > > Retrieving schema at 'ProbableCauses.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/network > > > > > Resources/Notifications.xsd'. > > > > > Retrieving schema at '../common/Definitions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/ > > > > > networkResources/ProbableCauses.xsd'. > > > > > Retrieving document at 'Exceptions.wsdl', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/Notification > > > > > Service.wsdl'. > > > > > Retrieving schema at 'xsd/interfaces/Exceptions.xsd', relative > > > > > to 'file:/D:/Jeromem/Code/axis2/wsdl/ > > > > > Exceptions.wsdl'. > > > > > Retrieving schema at '../common/Header.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/inter > > > > > faces/Exceptions.xsd'. > > > > > Retrieving schema at 'VendorExtensions.xsd', relative to > > > > > 'file:/D:/Jeromem/Code/axis2/wsdl/xsd/inter > > > > > faces/Exceptions.xsd'. > > > > > Exception in thread "main" > > > > > org.apache.axis2.wsdl.codegen.CodeGenerationException: > > > > > java.lang.RuntimeE > > > > > xception: java.lang.reflect.InvocationTargetException > > > > > at > > > > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(Co > > > > > de > > > > > Ge > > > > > nera > > > > > tionEngine.java:185 > > > > > ) > > > > > at > > > > > org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) > > > > > at > > > > > org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) > > > > > Caused by: java.lang.RuntimeException: > > > > > java.lang.reflect.InvocationTargetException > > > > > at > > > > > > > > > org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage > > > > (X > > > > ML > > > > Bean > > > > sExtension.java:9 > > > > > 3) > > > > > at > > > > > > > > > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(Code > > > > Ge > > > > ne > > > > rati > > > > onEngine.java:140 > > > > > ) > > > > > ... 2 more > > > > > Caused by: java.lang.reflect.InvocationTargetException > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > > > > Method) > > > > > at > > > > > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor > > > > Im > > > > pl > > > > .jav > > > > a:39) > > > > > at > > > > > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod > > > > Ac > > > > ce > > > > ssor > > > > Impl.java:25) > > > > > at java.lang.reflect.Method.invoke(Method.java:585) > > > > > at > > > > > > > > > org.apache.axis2.wsdl.codegen.extension.XMLBeansExtension.engage > > > > (X > > > > ML > > > > Bean > > > > sExtension.java:8 > > > > > 3) > > > > > ... 3 more > > > > > Caused by: java.lang.RuntimeException: > > > > > org.apache.xmlbeans.XmlException: D:\Jeromem\Code\axis2\xsd\i > > > > > nterfaces\NotificationService.xsd:29:40: error: > > > > > src-resolve: type '[EMAIL PROTECTED]' not found. > > > > > at > > > > > > > > > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(C > > > > od > > > > eG > > > > ener > > > > ationUtility.java > > > > > :192) > > > > > ... 8 more > > > > > Caused by: org.apache.xmlbeans.XmlException: > > > > > D:\Jeromem\Code\axis2\xsd\interfaces\NotificationServic > > > > > e.xsd:29:40: error: src-resolve: type '[EMAIL PROTECTED]' not > found. > > > > > at > > > > > > > > > org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile > > > > (S > > > > ch > > > > emaT > > > > ypeSystemCompiler > > > > > .java:225) > > > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > > > > Method) > > > > > at > > > > > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor > > > > Im > > > > pl > > > > .jav > > > > a:39) > > > > > at > > > > > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod > > > > Ac > > > > ce > > > > ssor > > > > Impl.java:25) > > > > > at java.lang.reflect.Method.invoke(Method.java:585) > > > > > at > > > > > org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:665) > > > > > at > > > > > > > > > org.apache.axis2.xmlbeans.CodeGenerationUtility.processSchemas(C > > > > od > > > > eG > > > > ener > > > > ationUtility.java > > > > > :161) > > > > > ... 8 more > > > > > > > > > > > > > ---------------------------------------------------------------- > > > > -- > > > > -- > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > ---------------------------------------------------------------- > > > > -- > > > > -- > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -------------------------------------------------------------------- > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
