Hi Sehil, What you have to do is as follows.
1. change the namespace of the dpcument to WSDL 2.0 namespace 2. Replace the portType section with the interface section 3. Get rid of message elements (WSDL 2.0 has got rid of messages, the operation directly refers to the schemaElemet) Thats it. Here is your WSDL 2.0 doc. If you had the schema inline (just copy IFX170.xsd into ur types section) you could have used the converter located at http://tools.wso2.org:19762/wservices/WSDLConverter/ Thanks, Keith. <?xml version="1.0" encoding="UTF-8"?> <description name="IFX170PortType" targetNamespace="urn:ifxforum-org:1:PortType" xmlns:tns="urn:ifxforum-org:1:PortType" xmlns:types="urn:ifxforum-org:1:PortType:types" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns="http://www.w3.org/ns/wsdl"; xmlns:wsoap="http://www.w3.org/ns/wsdl/soap"; xmlns:soap="http://www.w3.org/2003/05/soap-envelope";> <types> <xsd:schema targetNamespace="urn:ifxforum-org:1:PortType:types" xmlns:ifx="urn:ifxforum-org:XSD:1" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified"> <xsd:import namespace="urn:ifxforum-org:XSD:1" schemaLocation="IFX170.xsd"/> <xsd:element name="DoIFXRq"> <xsd:complexType> <xsd:sequence> <xsd:element ref="ifx:IFX"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="DoIFXRs"> <xsd:complexType> <xsd:sequence> <xsd:element ref="ifx:IFX"/> </xsd:sequence> </xsd:complexType> </xsd:element> </xsd:schema> </types> <interface name="IFX170PortType"> <operation name="DoIFX"> <input element="types:DoIFXRq"/> <output element="types:DoIFXRs"/> </operation> </interface> </description> Thanks, Keith. On 7/30/07, Snehil Brajpuriya <[EMAIL PROTECTED]> wrote: > > Hi Keith, > > Sorry for missing axis-user list. > > Yes it would be really great if this can be translated to 1.2/2.0. > > Really appreciate your help. > > > > Thanks > > Snehil > > > > > ------------------------------ > > *From:* keith chapman [mailto:[EMAIL PROTECTED] > *Sent:* Monday, July 30, 2007 2:05 PM > *To:* [EMAIL PROTECTED] > *Subject:* Re: [Axis2] Problem using SOAP12 vs SOAP11? > > > > Hi Sehil, > > This is a WSDL 1.1 document (Look at the namespace > http://schemas.xmlsoap.org/wsdl/, WSDL 2.0 uses the namespace > http://www.w3.org/ns/wsdl). Do you want a corresponding WSDL 2.0 document > for this WSDL 1.1 document? Its better to raise these question on > Axis2-user list though cause these might help other uses too. If you want > more help please post your question to the axis2 user list. > > Thanks, > Keith. > > On 7/30/07, *Snehil Brajpuriya* <[EMAIL PROTECTED]> wrote: > > Hi Keith, > > > > Is following a WSDL 2.0 document? > > > > <?xml version="1.0" encoding="UTF-8"?> > > <wsdl:definitions > > name="IFX170PortType" > > targetNamespace="urn:ifxforum-org:WSDL:1:PortType" > > xmlns:tns="urn:ifxforum-org:WSDL:1:PortType" > > xmlns:types="urn:ifxforum-org:WSDL:1:PortType:types" > > xmlns:wsdl=" http://schemas.xmlsoap.org/wsdl/"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > <wsdl:types> > > <xsd:schema > > > targetNamespace="urn:ifxforum-org:WSDL:1:PortType:types" > > xmlns:ifx="urn:ifxforum-org:XSD:1" > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > elementFormDefault="qualified"> > > <xsd:import > namespace="urn:ifxforum-org:XSD:1" > > schemaLocation="IFX170.xsd"/> > > <xsd:element name="DoIFXRq"> > > <xsd:complexType> > > <xsd:sequence> > > > <xsd:element ref="ifx:IFX" /> > > > </xsd:sequence> > > </xsd:complexType> > > </xsd:element> > > <xsd:element name="DoIFXRs"> > > <xsd:complexType> > > <xsd:sequence> > > > <xsd:element ref="ifx:IFX" /> > > > </xsd:sequence> > > </xsd:complexType> > > </xsd:element> > > </xsd:schema> > > </wsdl:types> > > <wsdl:message name="DoIFXRqMsg"> > > <wsdl:part name="parameters" > element="types:DoIFXRq"/> > > </wsdl:message> > > <wsdl:message name="DoIFXRsMsg"> > > <wsdl:part name="result" element="types:DoIFXRs"/> > > </wsdl:message> > > <wsdl:portType name="IFX170PortType"> > > <wsdl:operation name="DoIFX"> > > <wsdl:input message="tns:DoIFXRqMsg"/> > > <wsdl:output > message="tns:DoIFXRsMsg"/> > > </wsdl:operation> > > </wsdl:portType> > > </wsdl:definitions> > > > > > > I still haven't got any clarity on which style to use when. Can you assist > here? > > > > Thanks a lot > > Snehil > > > ------------------------------ > > *From:* keith chapman [mailto:[EMAIL PROTECTED] > *Sent:* Friday, July 27, 2007 5:14 PM > > > *To:* [EMAIL PROTECTED] > *Subject:* Re: [Axis2] Problem using SOAP12 vs SOAP11? > > > > No promlem you can ask anything related to WSDL 2.0. Will be more than > happy to help you. > > Thanks, > Keith. > > On 7/27/07, *Snehil Brajpuriya* < [EMAIL PROTECTED]> wrote: > > Thanks a ton for your help. > > Will definitely bother you again in case of queries J > > > > Regards > > Snehil > > > ------------------------------ > > *From:* keith chapman [mailto: [EMAIL PROTECTED] > *Sent:* Friday, July 27, 2007 4:15 PM > *To:* [EMAIL PROTECTED] > > > *Subject:* Re: [Axis2] Problem using SOAP12 vs SOAP11? > > > > Hi *Snehil, > > *The WSDL 2.0 primer[1] is a good starting point for WSDL 2.0. WSDL 2.0does > not have the concept of styles (rpc, document and so on) So you dont > have to worry about it. Axis 2 supports WSDL 2.0 so you can use it with > ease. Please let us know if you have any problems. > > Thanks, > Keith > > [1] http://www.w3.org/TR/wsdl20-primer/ > > On 7/27/07, *Snehil Brajpuriya* <[EMAIL PROTECTED] > wrote: > > Can anybody point to a good tutorial/article on differences in WSDL > versions(1.2,2.0 mainly) and also differences in styles(RPC, > Document,literal etc.). I need to decide a suitable one for the web services > I am developing. > > > > Thanks > > Snehil > > > ------------------------------ > > *From:* keith chapman [mailto: [EMAIL PROTECTED] > *Sent:* Friday, July 27, 2007 2:29 PM > *To:* [email protected] > *Subject:* Re: [Axis2] Problem using SOAP12 vs SOAP11? > > > > Here are the details. > http://www.w3.org/TR/soap12-part2/#http-respbindprocess > > Thanks, > Keith. > > On 7/27/07, *keith chapman* <[EMAIL PROTECTED]> wrote: > > Ho Jose, > > This is not a bug. The SOAP 1.2 specification mentions that we should send > HTTP code 400 in a fault if the fault code is soap:Sender. This is the > reason for getting 400 when using SOAP 1.2 and 500 when using SOAP 1.1. > > Thanks, > Keith. > > > > On 7/27/07, *Jose Luis Alba* < [EMAIL PROTECTED]> wrote: > > Hi, > > Recently I've been working on a test web service in Axis2 (1.3-RC1). That > service launchs checked exceptions but the behavior is different if I use > SOAP11 or SOAP12 from the client. > > When I use SOAP12 all responses from my exceptions are and AxisFault with > error 400: Bad request. (That's done in MessageContextBuilder -> > createFaultEnvelope -> getSenderFaultCode) > > When I use SOAP11 from the client I receive and AxisFault but this time > with an status error 500 and with the message of my exception. That's is > what I excepted! > > Why this behavior? > There's a bug in the SOAP12? > I'm missing something? > > Thanks, > > Jose > ------------------------------ > > > Sé un Mejor Amante del Cine > ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! > <http://us.rd.yahoo.com/mail/es/tagline/beabetter/*http:/advision.webevents.yahoo.com/reto/entretenimiento.html> > . > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > > http://www.patni.com > World-Wide Partnerships. World-Class Solutions. > _____________________________________________________________________ > > This e-mail message may contain proprietary, confidential or legally > privileged information for the sole use of the person or entity to whom this > message was originally addressed. Any review, e-transmission dissemination > or other use of or taking of any action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. If you > have received this e-mail in error kindly delete this e-mail from your > records. If it appears that this mail has been forwarded to you without > proper authority, please notify us immediately at [EMAIL PROTECTED] and > delete this mail. > _____________________________________________________________________ > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > > http://www.patni.com > World-Wide Partnerships. World-Class Solutions. > _____________________________________________________________________ > > This e-mail message may contain proprietary, confidential or legally > privileged information for the sole use of the person or entity to whom this > message was originally addressed. Any review, e-transmission dissemination > or other use of or taking of any action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. If you > have received this e-mail in error kindly delete this e-mail from your > records. If it appears that this mail has been forwarded to you without > proper authority, please notify us immediately at [EMAIL PROTECTED] and > delete this mail. > _____________________________________________________________________ > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > > http://www.patni.com > World-Wide Partnerships. World-Class Solutions. > _____________________________________________________________________ > > This e-mail message may contain proprietary, confidential or legally > privileged information for the sole use of the person or entity to whom this > message was originally addressed. Any review, e-transmission dissemination > or other use of or taking of any action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. If you > have received this e-mail in error kindly delete this e-mail from your > records. If it appears that this mail has been forwarded to you without > proper authority, please notify us immediately at [EMAIL PROTECTED] and > delete this mail. > _____________________________________________________________________ > > > > > -- > Keith Chapman > WSO2 Inc. > Oxygen for Web Services Developers. > http://wso2.org/ > > http://www.patni.com > World-Wide Partnerships. World-Class Solutions. > _____________________________________________________________________ > > This e-mail message may contain proprietary, confidential or legally > privileged information for the sole use of the person or entity to whom this > message was originally addressed. Any review, e-transmission dissemination > or other use of or taking of any action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. If you > have received this e-mail in error kindly delete this e-mail from your > records. If it appears that this mail has been forwarded to you without > proper authority, please notify us immediately at [EMAIL PROTECTED] and > delete this mail. > _____________________________________________________________________ > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
