Re: issues moving to axis2 from axis 1.4

Davanum Srinivas Fri, 20 Jul 2007 09:17:29 -0700

looks ok to me. Please try 1.2 RC2 and log a bug report if you still
see this issue. With details on your soap messages and code.


thanks,
dims

On 7/20/07, Steve Kruse <[EMAIL PROTECTED]> wrote:





Can someone tell me if they see any issues with the wsdl below.  I'm using
it for axis 1.4 and it works fine, but for axis2 I keep getting a cast
issue?  I am not sure if it is an xmlbeans issue or a wsdl issue.



<?xml version="1.0" encoding="UTF-8"?>

<wsdl:definitions targetNamespace="urn:soap.mdiapps.peoiws5"

    xmlns:apachesoap="http://xml.apache.org/xml-soap";

    xmlns:impl="urn:soap.mdiapps.peoiws5"

    xmlns:cvg="urn:data.soap.mdiapps.peoiws5"

    xmlns:ce="urn:exception.soap.mdiapps.peoiws5"

    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";

    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";

    xmlns:xsd="http://www.w3.org/2001/XMLSchema";>

    <wsdl:import
namespace="urn:trackinfo.lite.soap.mdiapps.peoiws5"
location="./xsd/lite/lite-track-info.xsd"/>

    <wsdl:import namespace="urn:exception.soap.mdiapps.peoiws5"
location="./xsd/exception.xsd"/>



    <wsdl:types>

        <xsd:schema

            elementFormDefault="qualified"

            targetNamespace="urn:soap.mdiapps.peoiws5"

            xmlns="http://www.w3.org/2001/XMLSchema";>

            <xsd:element name="handleTrackInfoLiteEvent">

                <xsd:complexType>

                    <xsd:sequence>

                        <xsd:element name="eventHolder"
type="cvg:InfoObjectEventBeanHolder"/>

                    </xsd:sequence>

                </xsd:complexType>

            </xsd:element>

            <xsd:element
name="handleTrackInfoLiteEventResponse">

                <xsd:complexType/>

            </xsd:element>

            <xsd:element name="handleTrackInfoLiteEvents">

                <xsd:complexType>

                    <xsd:sequence>

                        <xsd:element name="eventsHolder"
type="cvg:InfoObjectEventBeansHolder" />

                    </xsd:sequence>

                </xsd:complexType>

            </xsd:element>

            <xsd:element
name="handleTrackInfoLiteEventsResponse">

                <xsd:complexType />

            </xsd:element>

            <xsd:element name="fault" type="ce:CommunicationException"/>

            <xsd:element name="fault1"
type="ce:ServiceUnavailableException"/>

        </xsd:schema>

    </wsdl:types>



    <wsdl:message name="handleTrackInfoLiteEventsResponse">

        <wsdl:part
element="impl:handleTrackInfoLiteEventsResponse"
name="parameters" />

    </wsdl:message>

    <wsdl:message name="handleTrackInfoLiteEventResponse">

        <wsdl:part
element="impl:handleTrackInfoLiteEventResponse"
name="parameters"/>

    </wsdl:message>

    <wsdl:message name="handleTrackInfoLiteEventsRequest">

        <wsdl:part element="impl:handleTrackInfoLiteEvents"
name="parameters" />

    </wsdl:message>

    <wsdl:message name="CommunicationException">

        <wsdl:part element="impl:fault" name="fault"/>

    </wsdl:message>

    <wsdl:message name="handleTrackInfoLiteEventRequest">

        <wsdl:part element="impl:handleTrackInfoLiteEvent"
name="parameters"/>

    </wsdl:message>

    <wsdl:message name="ServiceUnavailableException">

        <wsdl:part element="impl:fault1" name="fault"/>

    </wsdl:message>



    <wsdl:portType name="TrackLiteDataHandlerWS">

        <wsdl:operation name="handleTrackInfoLiteEvent">

            <wsdl:input
message="impl:handleTrackInfoLiteEventRequest"
name="handleTrackInfoLiteEventRequest"/>

            <wsdl:output
message="impl:handleTrackInfoLiteEventResponse"
name="handleTrackInfoLiteEventResponse"/>

            <wsdl:fault message="impl:CommunicationException"
name="CommunicationException"/>

            <wsdl:fault
message="impl:ServiceUnavailableException"
name="ServiceUnavailableException"/>

        </wsdl:operation>

        <wsdl:operation name="handleTrackInfoLiteEvents">

            <wsdl:input
message="impl:handleTrackInfoLiteEventsRequest"
name="handleTrackInfoLiteEventsRequest" />

            <wsdl:output
message="impl:handleTrackInfoLiteEventsResponse"
name="handleTrackInfoLiteEventsResponse" />

            <wsdl:fault message="impl:CommunicationException"
name="CommunicationException" />

            <wsdl:fault
message="impl:ServiceUnavailableException"
name="ServiceUnavailableException" />

        </wsdl:operation>

    </wsdl:portType>



    <wsdl:binding name="TrackLiteDataHandlerWSSoapBinding"
type="impl:TrackLiteDataHandlerWS">

        <wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>

        <wsdl:operation name="handleTrackInfoLiteEvent">

            <wsdlsoap:operation soapAction=""/>

            <wsdl:input
name="handleTrackInfoLiteEventRequest">

                <wsdlsoap:body use="literal"/>

            </wsdl:input>

            <wsdl:output
name="handleTrackInfoLiteEventResponse">

                <wsdlsoap:body use="literal"/>

            </wsdl:output>

            <wsdl:fault name="CommunicationException">

                <wsdlsoap:fault name="CommunicationException"
use="literal"/>

            </wsdl:fault>

            <wsdl:fault name="ServiceUnavailableException">

                <wsdlsoap:fault name="ServiceUnavailableException"
use="literal"/>

            </wsdl:fault>

        </wsdl:operation...

[Message clipped]



--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: issues moving to axis2 from axis 1.4

Reply via email to