facebook

Another problematic WSDL

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #270861 Reply

    Here’s a WSDL. It passes MyEclipse 5.5.1 validation; however, I get the generic “Error generating service” dialog when attempting to build a client. I see on XFire’s site that 1.2.6 fixed a regression where unbounded elements generated incorrect Java files, but that one liner doesn’t say what version the regression appeared in, or how they were affected…. may or may not be indicative of the problem MyEclipse is having.

    <?xml version=”1.0″ encoding=”utf-8″?>
    <definitions name=”RDM”
    xmlns=”http://schemas.xmlsoap.org/wsdl/&#8221;
    targetNamespace=”http://www.sas.com/xml/analytics/rdm-1.1/wsdl/&#8221;
    xmlns:tns=”http://www.sas.com/xml/analytics/rdm-1.1/wsdl/&#8221;
    xmlns:typesns=”http://www.sas.com/xml/analytics/rdm-1.1&#8243;
    xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”&gt;

    <types>
    <schema xmlns=”http://www.w3.org/2001/XMLSchema&#8221;
    targetNamespace=”http://www.sas.com/xml/analytics/rdm-1.1&#8243;
    xmlns:tns=”http://www.sas.com/xml/analytics/rdm-1.1&#8243;
    elementFormDefault=”qualified”>

    <annotation>
    <documentation>
    Schema for SAS RDM ‘CustomerCall2’ Event.
    Generated on Fri, 11 May 2007 10:40:50 -0400.
    </documentation>
    </annotation>

    <element name=”String”>
    <complexType>
    <sequence>
    <element name=”Val” type=”string” minOccurs=”0″/>
    </sequence>
    </complexType>
    </element>
    <element name=”StringArray”>
    <complexType>
    <sequence>
    <element name=”Val” minOccurs=”0″>
    <complexType>
    <sequence>
    <element name=”Item” type=”string” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>

    <element name=”Int”>
    <complexType>
    <sequence>
    <element name=”Val” type=”long” minOccurs=”0″/>
    </sequence>
    </complexType>
    </element>
    <element name=”IntArray”>
    <complexType>
    <sequence>
    <element name=”Val” minOccurs=”0″>
    <complexType>
    <sequence>
    <element name=”Item” type=”long” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>

    <element name=”Float”>
    <complexType>
    <sequence>
    <element name=”Val” type=”double” minOccurs=”0″/>
    </sequence>
    </complexType>
    </element>
    <element name=”FloatArray”>
    <complexType>
    <sequence>
    <element name=”Val” minOccurs=”0″>
    <complexType>
    <sequence>
    <element name=”Item” type=”double” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>

    <element name=”Boolean”>
    <complexType>
    <sequence>
    <element name=”Val” type=”boolean” minOccurs=”0″/>
    </sequence>
    </complexType>
    </element>
    <element name=”BooleanArray”>
    <complexType>
    <sequence>
    <element name=”Val” minOccurs=”0″>
    <complexType>
    <sequence>
    <element name=”Item” type=”boolean” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>

    <element name=”DateTime”>
    <complexType>
    <sequence>
    <element name=”Val” type=”dateTime” minOccurs=”0″/>
    </sequence>
    </complexType>
    </element>
    <element name=”DateTimeArray”>
    <complexType>
    <sequence>
    <element name=”Val” minOccurs=”0″>
    <complexType>
    <sequence>
    <element name=”Item” type=”dateTime” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </element>
    </sequence>
    </complexType>
    </element>

    <annotation>
    <documentation>
    Input-Type-Mapping:
    [CustomerID:String],
    [Amount:Float],
    [Mood:String],
    [SigEvent:String]
    </documentation>
    </annotation>
    <complexType name=”DataItemType”>
    <choice>
    <element ref=”tns:String”/>
    <element ref=”tns:Float”/>
    </choice>
    <attribute name=”name” use=”required”>
    <simpleType>
    <restriction base=”string”>
    <enumeration value=”CustomerID”/>
    <enumeration value=”Amount”/>
    <enumeration value=”Mood”/>
    <enumeration value=”SigEvent”/>
    </restriction>
    </simpleType>
    </attribute>
    </complexType>

    <annotation>
    <documentation>
    Output-Type-Mapping:
    [cid:String],
    [OfferStrings:StringArray],
    [OfferFloats:FloatArray],
    [NextQuestions:StringArray]
    </documentation>
    </annotation>
    <complexType name=”DataItemResponseType”>
    <choice>
    <element ref=”tns:String”/>
    <element ref=”tns:StringArray”/>
    <element ref=”tns:FloatArray”/>
    </choice>
    <attribute name=”name” use=”required”>
    <simpleType>
    <restriction base=”string”>
    <enumeration value=”cid”/>
    <enumeration value=”OfferStrings”/>
    <enumeration value=”OfferFloats”/>
    <enumeration value=”NextQuestions”/>
    </restriction>
    </simpleType>
    </attribute>
    </complexType>

    <complexType name=”HeaderType”>
    <sequence>
    <element name=”Identity” type=”string” minOccurs=”0″/>
    </sequence>
    </complexType>

    <complexType name=”HeaderResponseType”>
    <sequence>
    <element name=”CorrelationId” type=”string” minOccurs=”0″/>
    <element name=”StartTime” type=”string”/>
    <element name=”CompletionTime” type=”string”/>
    </sequence>
    </complexType>

    <complexType name=”BodyType”>
    <sequence>
    <element name=”Data” type=”tns:DataItemType” minOccurs=”4″ maxOccurs=”4″/>
    </sequence>
    </complexType>

    <complexType name=”BodyResponseType”>
    <sequence>
    <element name=”Data” type=”tns:DataItemResponseType” minOccurs=”4″ maxOccurs=”4″/>
    </sequence>
    </complexType>

    <complexType name=”EventType”>
    <sequence>
    <element name=”Header” type=”tns:HeaderType” minOccurs=”0″/>
    <element name=”Body” type=”tns:BodyType”/>
    </sequence>
    <attribute name=”name” type=”string” use=”required” fixed=”CustomerCall2″/>
    </complexType>

    <complexType name=”EventResponseType”>
    <sequence>
    <element name=”Header” type=”tns:HeaderResponseType”/>
    <element name=”Body” type=”tns:BodyResponseType”/>
    </sequence>
    <attribute name=”name” type=”string” use=”required” fixed=”CustomerCall2″/>
    </complexType>

    <element name=”Event” type=”tns:EventType”/>
    <element name=”EventResponse” type=”tns:EventResponseType”/>

    <element name=”FaultException” type=”tns:FaultException”/>
    <complexType name=”FaultException”>
    <sequence>
    <element name=”ExceptionMessage” type=”string” minOccurs=”0″ maxOccurs=”unbounded”/>
    </sequence>
    </complexType>
    </schema>
    </types>

    <message name=”eventRequest”>
    <part name=”parameters” element=”typesns:Event”/>
    </message>
    <message name=”eventResponse”>
    <part name=”parameters” element=”typesns:EventResponse”/>
    </message>
    <message name=”FaultException”>
    <part name=”detail” element=”typesns:FaultException”/>
    </message>

    <portType name=”EventPortType”>
    <operation name=”Event”>
    <input message=”tns:eventRequest”/>
    <output message=”tns:eventResponse”/>
    <fault name=”fault” message=”tns:FaultException”/>
    </operation>
    </portType>

    <binding name=”EventSoapBinding” type=”tns:EventPortType”>
    <soap:binding transport=”http://schemas.xmlsoap.org/soap/http&#8221; style=”document”/>
    <operation name=”Event”>
    <soap:operation soapAction=””/>
    <input>
    <soap:body use=”literal”/>
    </input>
    <output>
    <soap:body use=”literal”/>
    </output>
    <fault name=”fault”>
    <soap:fault name=”fault” use=”literal”/>
    </fault>
    </operation>
    </binding>

    <service name=”EventService”>
    <port name=”EventPort” binding=”tns:EventSoapBinding”>
    <soap:address location=”http://localhost/RDM/Event”/&gt;
    </port>
    </service>
    </definitions>

    #270944 Reply

    Riyad Kalla
    Member

    This looks like a problem with generation, we’ll look into it ASAP. Thank you for including your WSDL.

    #271016 Reply

    Brian Fernandes
    Moderator

    Hi,

    We were able to replicate this issue easily, there seems to be an issue with the client generator which I’ve filed and should be fixed in the next release.

    In the meanwhile, you could use the Service generation wizard with the “Generate Test client” option checked. The code generated is essentially the same except for an extra service implementation class which you could delete.

    Thanks for sharing your WSDL file, inconvenience regretted. Let us know if you require further assistance.

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: Another problematic WSDL

You must be logged in to post in the forum log in