Right. That makes sense and the soap12 one must be changed as well. Ok so using the same batch file as before and making those changes (see below). I am now back to yesterday's error message about the message exchange pattern. Where is this http://www.w3.org/2004/03/wsdl/in-outcoming from?
>wsdl2java.bat -uri hilton2.wsdl -wv 2.0 Using AXIS2_HOME: C:\Java\axis2-1.3RC2 Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01 Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>( CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: org.apache.axis2.AxisFault: An unsupported message exchange pattern (MEP) exists in ID is http://www.w3.org/2004/03/wsdl/in-out ... ----- hilton2.wsdl ----- <description xmlns="http://www.w3.org/ns/wsdl"; targetNamespace= "http://greath.example.com/2004/wsdl/resSvc.wsdl"; xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"; xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"; xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap"; xmlns:soap="http://www.w3.org/2003/05/soap-envelope";> <documentation> This document describes the GreatH Web service. Additional application-level requirements for use of this service -- beyond what WSDL 2.0 is able to describe -- are available at http://greath.example.com/2004/reservation-documentation.html </documentation> <types> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"; targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd"; xmlns="http://greath.example.com/2004/schemas/resSvc.xsd";> <xs:element name="checkAvailability" type="tCheckAvailability"/> <xs:complexType name="tCheckAvailability"> <xs:sequence> <xs:element name="checkInDate" type="xs:date"/> <xs:element name="checkOutDate" type="xs:date"/> <xs:element name="roomType" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:element name="checkAvailabilityResponse" type="xs:double"/> <xs:element name="invalidDataError" type="xs:string"/> </xs:schema> </types> <interface name = "reservationInterface" > <fault name = "invalidDataFault" element = "ghns:invalidDataError"/> <operation name="opCheckAvailability" pattern="http://www.w3.org/2004/03/wsdl/in-out"; > <input messageLabel="In" element="ghns:checkAvailability" /> <output messageLabel="Out" element="ghns:checkAvailabilityResponse" /> <outfault ref="tns:invalidDataFault" messageLabel="Out"/> </operation> </interface> <binding name="reservationSOAPBinding" interface="tns:reservationInterface" type="http://www.w3.org/ns/wsdl/soap"; wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";> <operation ref="tns:opCheckAvailability" wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/> <fault ref="tns:invalidDataFault" wsoap:code="soap:Sender"/> </binding> <service name="reservationService" interface="tns:reservationInterface"> <endpoint name="reservationEndpoint" binding="tns:reservationSOAPBinding" address ="http://greath.example.com/2004/reservation"/> </service> </description> On 8/2/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > > Make sure you're using the correct WSDL namespace. > > You're currently using " > http://www.w3.org/2004/08/wsdl";<http://www.w3.org/2004/08/wsdl%7Ddescription> > > You should be using > "http://www.w3.org/ns/wsdl<http://www.w3.org/ns/wsdl%7Ddescription>" > > Anne > > On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote: > > > > Hi Keith, > > > > Thanks for looking at this. I'm reading your message and I'm > > confused. I am using Axis2 1.3 RC2 which is the latest RC from the url > > you listed. If you are using the same one, then perhaps I have some kind of > > pilot error in my wsdl2java usage. Actually I seem to be heading full speed > > into reverse because now the error message is > > > > Using AXIS2_HOME: > > > > ---------------------------- > > Here's my fancy batch file: > > > > echo %AXIS2_HOME% > > wsdl2java.bat -uri hilton.wsdl -wv 2.0 > > ----------------------------- > > and I get > > > > Using AXIS2_HOME: c:\Java\axis2-1.3RC2 > > Using JAVA_HOME: c:\Program Files\Java\jre1.6.0_01 > > Woden[Fatal Error],0:0, WSDL501, Expected a "{ > > http://www.w3.org/ns/wsdl}description<http://www.w3.org/ns/wsdl%7Ddescription>" > > element, but found a "{ > > http://www.w3.org/2004/08/wsdl}description<http://www.w3.org/2004/08/wsdl%7Ddescription>" > > element instead. > > Exception in thread "main" > > org.apache.axis2.wsdl.codegen.CodeGenerationException: Error in parsing > > WSDL > > ... > > > > But maybe this isn't so weird because the w3c example uses > > > > <description > > xmlns="http://www.w3.org/2004/08/wsdl"; > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl " > > > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"; > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd"; > > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 " > > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";> > > > > and I thought that xmlns should be http://www.w3.org/ns/wsdl > > but then I am less clear on what other changes should be made does > > www.w3.org/2004/08/wsdl/soap12 > > become www.w3.org/ns/wsdl/soap12 ? > > > > Could you send me the example wsdl you used successfully? > > > > Thanks > > > > > > > > > > --------------------------------- > > > > Here's the hilton wsdl > > > > --------------------------------- > > > > <description > > xmlns="http://www.w3.org/2004/08/wsdl"; > > targetNamespace= " http://greath.example.com/2004/wsdl/resSvc.wsdl " > > > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl"; > > xmlns:ghns = " http://greath.example.com/2004/schemas/resSvc.xsd"; > > xmlns:wsoap= "http://www.w3.org/2004/08/wsdl/soap12 " > > xmlns:soap=" http://www.w3.org/2003/05/soap-envelope";> > > > > <documentation> > > This document describes the GreatH Web service. Additional > > application-level requirements for use of this service -- > > beyond what WSDL 2.0 is able to describe -- are available > > at http://greath.example.com/2004/reservation-documentation.html > > </documentation> > > > > <types> > > <xs:schema > > xmlns:xs="http://www.w3.org/2001/XMLSchema " > > > > targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd > > " > > xmlns="http://greath.example.com/2004/schemas/resSvc.xsd "> > > > > <xs:element name="checkAvailability" > > type="tCheckAvailability"/> > > <xs:complexType name="tCheckAvailability"> > > <xs:sequence> > > <xs:element name="checkInDate" type="xs:date"/> > > <xs:element name="checkOutDate" type="xs:date"/> > > <xs:element name="roomType" type="xs:string"/> > > </xs:sequence> > > </xs:complexType> > > > > <xs:element name="checkAvailabilityResponse" type="xs:double"/> > > > > > > <xs:element name="invalidDataError" type="xs:string"/> > > > > </xs:schema> > > </types> > > > > <interface name = "reservationInterface" > > > > > <fault name = "invalidDataFault" > > element = "ghns:invalidDataError"/> > > > > <operation name="opCheckAvailability" > > pattern=" http://www.w3.org/2004/03/wsdl/in-out"; > > > <input messageLabel="In" > > element="ghns:checkAvailability" /> > > <output messageLabel="Out" > > element="ghns:checkAvailabilityResponse" /> > > <outfault ref="tns:invalidDataFault" messageLabel="Out"/> > > </operation> > > > > </interface> > > > > <binding name="reservationSOAPBinding" > > interface="tns:reservationInterface" > > type=" http://www.w3.org/2004/08/wsdl/soap12 " > > wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP";> > > > > > > <operation ref="tns:opCheckAvailability" > > wsoap:mep=" > > http://www.w3.org/2003/05/soap/mep/request-response"/<http://www.w3.org/2003/05/soap/mep/request-response%22/>> > > > > > > <fault ref="tns:invalidDataFault" > > wsoap:code="soap:Sender"/> > > > > </binding> > > > > <service name="reservationService" > > interface="tns:reservationInterface"> > > > > <endpoint name="reservationEndpoint" > > binding="tns:reservationSOAPBinding" > > address =" http://greath.example.com/2004/reservation"/ > > <http://greath.example.com/2004/reservation%22/>> > > > > </service> > > > > </description> > > > > > > > > ** > > > > On 8/2/07, New AxisU <[EMAIL PROTECTED]> wrote: > > > > > > Axis2 1.3 RC2 > > > > > > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote: > > > > > > > > Hi, > > > > > > > > I just tried the wsdl located at > > > > http://www.w3.org/TR/wsdl20-primer/#basics-greath-scenario in the > > > > primer with Axis2-1.3-RC2. It worked without any problems. WSDL > > > > 2.0support was only available in > > > > Axis2-1.2 prior to this. Please use the latest RC located at > > > > http://ws.apache.org/axis2/download.cgi. The 1.3 release will be out > > > > very soon. You can swtich to that once its released. The 1.3 release > > > > will be very stable. > > > > > > > > Thanks, > > > > Keith. > > > > > > > > On 8/2/07, keith chapman <[EMAIL PROTECTED] > wrote: > > > > > > > > > > Hi, > > > > > > > > > > Wats your Axis2 version? > > > > > > > > > > Thanks, > > > > > Keith. > > > > > > > > > > On 8/2/07, New AxisU <[EMAIL PROTECTED] > wrote: > > > > > > > > > > > > Hi, I am looking at migrating our wsdls from 1.1 to 2.0. I am > > > > > > using axis2 wsdl2java as a way of sanity checking the wsdls. I am > > > > > > seeing > > > > > > messages about "unsupported message exchange patterns". The wsdl > > > > > > below is > > > > > > much simpler than the one I'm using but it gets that same message. > > > > > > I got it > > > > > > from the w3c wsdl 2.0 primer. Any idea what is wrong with it? > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > > <description > > > > > > xmlns="http://www.w3.org/ns/wsdl"; > > > > > > targetNamespace= > > > > > > "http://greath.example.com/2004/wsdl/resSvc.wsdl " > > > > > > > > > > > > xmlns:tns= "http://greath.example.com/2004/wsdl/resSvc.wsdl " > > > > > > > > > > > > xmlns:ghns = "http://greath.example.com/2004/schemas/resSvc.xsd"; > > > > > > xmlns:wsoap= "http://www.w3.org/ns/wsdl/soap12 " > > > > > > xmlns:soap=" http://www.w3.org/ns/soap-envelope";> > > > > > > > > > > > > <documentation> > > > > > > This document describes the GreatH Web service. Additional > > > > > > application-level requirements for use of this service -- > > > > > > beyond what WSDL 2.0 is able to describe -- are available > > > > > > at > > > > > > http://greath.example.com/2004/reservation-documentation.html > > > > > > </documentation> > > > > > > > > > > > > <types> > > > > > > <xs:schema > > > > > > xmlns:xs="XMLSchema.xsd" > > > > > > > > > > > > targetNamespace="http://greath.example.com/2004/schemas/resSvc.xsd > > > > > > " > > > > > > xmlns="http://greath.example.com/2004/schemas/resSvc.xsd > > > > > > "> > > > > > > <xs:element name="checkAvailability" > > > > > > type="tCheckAvailability"/> > > > > > > <xs:complexType name="tCheckAvailability"> > > > > > > <xs:sequence> > > > > > > <xs:element name="checkInDate" type="xs:date"/> > > > > > > <xs:element name="checkOutDate" type="xs:date"/> > > > > > > > > > > > > <xs:element name="roomType" type="xs:string"/> > > > > > > </xs:sequence> > > > > > > </xs:complexType> > > > > > > <xs:element name="checkAvailabilityResponse" > > > > > > type="xs:double"/> > > > > > > <xs:element name="invalidDataError" type="xs:string"/> > > > > > > </xs:schema> > > > > > > </types> > > > > > > > > > > > > <interface name = "reservationInterface" > > > > > > > <fault name = "invalidDataFault" > > > > > > element = "ghns:invalidDataError"/> > > > > > > <operation name="opCheckAvailability" > > > > > > pattern=" http://www.w3.org/2004/03/wsdl/in-out " > > > > > > > <input messageLabel="In" > > > > > > element="ghns:checkAvailability" /> > > > > > > <output messageLabel="Out" > > > > > > element="ghns:checkAvailabilityResponse" /> > > > > > > <outfault ref="tns:invalidDataFault" > > > > > > messageLabel="Out"/> > > > > > > </operation> > > > > > > </interface> > > > > > > > > > > > > <binding name="reservationSOAPBinding" > > > > > > interface="tns:reservationInterface" > > > > > > type=" http://www.w3.org/2004/08/wsdl/soap12 " > > > > > > > > > > > > wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP > > > > > > "> > > > > > > <operation ref="tns:opCheckAvailability" > > > > > > > > > > > > wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"/<http://www.w3.org/2003/05/soap/mep/request-response%22/>> > > > > > > <fault ref="tns:invalidDataFault" > > > > > > wsoap:code="soap:Sender"/> > > > > > > </binding> > > > > > > > > > > > > <service name="reservationService" > > > > > > interface="tns:reservationInterface"> > > > > > > <endpoint name="reservationEndpoint" > > > > > > binding="tns:reservationSOAPBinding" > > > > > > address =" > > > > > > http://greath.example.com/2004/reservation"/<http://greath.example.com/2004/reservation%22/> > > > > > > > > > > > > > </service> > > > > > > </description> > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Keith Chapman > > > > > WSO2 Inc. > > > > > Oxygen for Web Services Developers. > > > > > http://wso2.org/ > > > > > > > > > > > > > > > > > > > > -- > > > > Keith Chapman > > > > WSO2 Inc. > > > > Oxygen for Web Services Developers. > > > > http://wso2.org/ > > > > > > > > > > > > >
