Re: [Axis2] wsdl2java with WSDL 2.0

Jack Sprat <[email protected]>
Newsgroups gmane.text.xml.axis.user
Message-ID <[email protected]>
I don't think I can attach files here so I have pasted the WSDL below.  There are 3 included schemas.  I have not included those here to keep this message from getting too long.  Can I send those to you off-list?



<?xml version="1.0" encoding="UTF-8"?>
<wsdl:description xmlns:wsdl="http://www.w3.org/ns/wsdl"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:ship="http://ws.estesexpress.com/schema/shipmenttracking"
    xmlns:tns="http://ws.estesexpress.com/shipmenttracking"
    targetNamespace="http://ws.estesexpress.com/shipmenttracking">

<!--
WSDL 2.0 version
-->

    <wsdl:documentation>Shipment tracking web service. Copyright 2012 Estes Express Lines, Inc.</wsdl:documentation>

    <!-- Define all types used in SOAP request/response here. -->
    <wsdl:types>
        <xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ws.estesexpress.com/shipmenttracking" targetNamespace="http://ws.estesexpress.com/shipmenttracking">
            <xsd:complexType name="AuthenticationType">
                <xsd:sequence>
                    <xsd:element name="user" type="tns:UserType"/>
                    <xsd:element name="password" type="tns:PasswordType"/>
                </xsd:sequence>
            </xsd:complexType>

            <xsd:simpleType name="EchoRequestType">
                <xsd:restriction base="xsd:string">
                    <xsd:maxLength value="100"/>
                </xsd:restriction>
            </xsd:simpleType>

            <xsd:simpleType name="PasswordType">
                <xsd:restriction base="xsd:string">
                    <xsd:minLength value="5"/>
                    <xsd:maxLength value="10"/>
                </xsd:restriction>
            </xsd:simpleType>

            <xsd:simpleType name="UserType">
                <xsd:restriction base="xsd:string">
                    <xsd:minLength value="5"/>
                    <xsd:maxLength value="10"/>
                </xsd:restriction>
            </xsd:simpleType>

            <!-- Define SOAP message names here. -->

            <!-- Authentication SOAP Header  -->
            <xsd:element name="auth" type="tns:AuthenticationType"/>

            <!-- General Fault -->
            <xsd:element name="generalError" type="xsd:string"/>

            <!-- Schema Validation Fault -->
            <xsd:element name="schemaError" type="xsd:string"/>

            <!-- Echo Request Type -->
            <xsd:element name="echoRequest" type="tns:EchoRequestType"/>
            <!-- Echo Response Type -->
            <xsd:element name="echoResponse" type="xsd:string"/>
        </xsd:schema>

        <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ws.estesexpress.com/schema/shipmenttracking" targetNamespace="http://ws.estesexpress.com/schema/shipmenttracking" xmlns:ship="http://ws.estesexpress.com/schema/shipmenttracking">
            <!--  Reference all the schemas -->
            <xsd:include schemaLocation="search.xsd"/>
            <xsd:include schemaLocation="results.xsd"/>
        </xsd:schema>
    </wsdl:types>

    <!-- Interfaces -->
    <wsdl:interface name="trackingInterface">
        <!-- Faults -->
        <wsdl:fault name="generalError" element="tns:generalError" />
        <wsdl:fault name="schemaError" element="tns:schemaError" />
        <!-- Echo operation -->
        <wsdl:operation name="echo" pattern="http://www.w3.org/ns/wsdl/in-out">
            <wsdl:input element="tns:echoRequest"/>
            <wsdl:output element="tns:echoResponse"/>
        </wsdl:operation>
        <!-- Shipment tracking search operation -->
        <wsdl:operation name="trackShipments" pattern="http://www.w3.org/ns/wsdl/in-out">
            <wsdl:input element="ship:search" xmlns:ship="http://ws.estesexpress.com/schema/shipmenttracking" />
            <wsdl:output element="ship:trackingInfo" xmlns:ship="http://ws.estesexpress.com/schema/shipmenttracking" />
        </wsdl:operation>
    </wsdl:interface>

    <!-- Concrete Binding with SOAP-->
    <wsdl:binding name="shipmentTrackingBinding" type="http://www.w3.org/ns/wsdl/http" interface="tns:trackingInterface" xmlns:wsoap="http://www.w3.org/ns/wsdl/soap">
        <wsdl:fault ref="tns:generalErrorMessage"/>
        <wsdl:fault ref="tns:schemaErrorMessage"/>
        <wsdl:operation ref="tns:echo" wsoap:soapAction="http://ws.estesexpress.com/shipmenttracking/echo"/>
        <wsdl:operation ref="tns:trackShipments" wsoap:soapAction="http://ws.estesexpress.com/shipmenttracking/trackShipments">
            <wsdl:input>
                <wsoap:header required="true" element="tns:auth"/>
            </wsdl:input>
            <wsdl:output/>
            <wsdl:outfault ref="tns:schemaErrorMessage"/>
            <wsdl:outfault ref="tns:generalErrorMessage"/>
        </wsdl:operation>
    </wsdl:binding>

    <!-- Define service and endpoint -->
    <wsdl:service name="ShipmentTrackingService" interface="tns:trackingInterface">
        <wsdl:documentation>Estes shipment tracking web service</wsdl:documentation>
        <wsdl:endpoint name="shipmentTracking" binding="tns:shipmentTrackingBinding"
                  address="https://www.estes-express.com/shipmenttracking/services/ShipmentTracking"/>
    </wsdl:service>
</wsdl:description>

Thanks,
J


________________________________
From: Shameera Rathnayaka <[email protected]>
To: [email protected]; Jack Sprat <[email protected]> 
Cc: "[email protected]" <[email protected]> 
Sent: Friday, March 29, 2013 9:28 AM
Subject: Re: [Axis2] wsdl2java with WSDL 2.0


could you please attached a sample WSDL which reproduce this error.

Regards,
Shameera.



On Fri, Mar 29, 2013 at 6:44 PM, Jack Sprat <[email protected]> wrote:

Yes, I used ADB binding (-d adb) and got the exact same error that was thrown using XMLBeans binding.
>
>
>The WSDL appears to be valid.  I tested with the Woden parser and also with XMLSpy.  The wsdl2java command throws an error with ADB or XMLBeans binding.
>
>How can I get past this problem?
>
>
>Thanks,
>J
>
>
>________________________________
>From: Shameera Rathnayaka <[email protected]>
>To: [email protected]; Jack Sprat <[email protected]>
>Cc: "[email protected]" <[email protected]>
>Sent: Thursday, March 28, 2013 11:44 PM
>
>Subject: Re: [Axis2] wsdl2java with WSDL 2.0
>
>
>Hi Jack,
>
>
>
>On Thu, Mar 28, 2013 at 9:15 PM, Jack Sprat <[email protected]> wrote:
>
>Same exact error using ADB binding.
>>
>>Please advise how to get past this problem.  I am really stuck!
>>
>>
>If you need to generated ADB binding, then use -d adb instead -d xmlbeans , BTW ADB is default binding, if you didn't specifically mentioned the -d option then binding would be ADB,  You can find more about this from here[1][2]
>
>Cheers,
>Shameera.
>
>[1]http://axis.apache.org/axis2/java/core/tools/CodegenToolReference.html
>[2]http://axis.apache.org/axis2/java/core/tools/
>
>
>Thanks,
>>J
>>
>>
>>
>>
>>----- Original Message -----
>>From: Sagara Gunathunga <[email protected]>
>>To: "[email protected]" <[email protected]>
>>Cc:
>>Sent: Tuesday, March 26, 2013 1:32 AM
>>Subject: Re: [Axis2] wsdl2java with WSDL 2.0
>>
>>On Tue, Mar 26, 2013 at 2:18 AM, Jack Sprat <[email protected]> wrote:
>>> Does the wsdl2java command work with a version 2.0 WSDL?  I have created a version 2.0 WSDL and validated it with Woden (included with Axis2 1.6.1).  The WSDL also passed validation using Altova XML Spy.  However, an error is thrown when I try to create the code stubs using wsdl2java.  Below is the command:
>>>
>>> call %AXIS2_HOME%/bin/WSDL2Java -uri C:\Data\MyWebService\docs\myServiceV2.0.wsdl -p com.mycompany.ws.myservice.producer.gensrc -d xmlbeans -s -ss -sd -ssi -wv 2.0 -o C:\Data\build\myservice
>>
>>I'm not quite sure it is well supported for xmlbeans try to use
>>default ADB it should work.
>>
>>Thanks !
>>>
>>> Thanks,
>>> J
>>>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.