bildwelt
E2E FORUM
E2E Bridge E2E Commerce

Incorrect assocotian

E2E Forum Modeling & Development Incorrect assocotian

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  Andi 2 years, 6 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1912

    frans
    Participant

    Please import the attached wsdl in a model.

    After importing, the class “MagentoApi.wsdl::Types::xml.apache.org.xml-soap::Schema::Types::Map” has 1 attribute, item.
    This is correct. But the Multiplicity is not correctly set, the imported has set it to 0..1, where as I expected 0…*.

    Any suggestions?

    This wsdl is a Magento V1 WSDL, but modified since E2E does not seem to handle the “anyType”.

    #1913

    frans
    Participant

    Cannot upload wsdl, so here it is:
    ———————————————-
    <?xml version=”1.0″ encoding=”UTF-8″?>
    <definitions xmlns:typens=”urn:Magento” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”
    xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/” xmlns=”http://schemas.xmlsoap.org/wsdl/”
    name=”Magento” targetNamespace=”urn:Magento”
    xmlns:ns2=”http://xml.apache.org/xml-soap”
    >
    <types>
    <schema xmlns=”http://www.w3.org/2001/XMLSchema” targetNamespace=”urn:Magento”>
    <!– <import namespace=”http://schemas.xmlsoap.org/soap/encoding/” schemaLocation=”http://schemas.xmlsoap.org/soap/encoding/” />–>
    <complexType name=”FixedArray”>
    <complexContent>
    <restriction base=”soapenc:Array”>
    <attribute ref=”soapenc:arrayType” wsdl:arrayType=”xsd:anyType[]” />
    </restriction>
    </complexContent>
    </complexType>
    </schema>

    <schema xmlns=”http://www.w3.org/2001/XMLSchema” targetNamespace=”http://xml.apache.org/xml-soap”
    xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/”
    >
    <complexType name=”Item”>
    <sequence>
    <element name=”key” type=”xsd:string”/>
    <element name=”value” type=”xsd:string”/>
    </sequence>
    </complexType>
    <complexType name=”Map”>
    <sequence>
    <element name=”item” minOccurs=”0″ maxOccurs=”unbounded” type=”ns2:Item” />
    </sequence>
    </complexType>
    </schema>
    </types>

    <message name=”call”>
    <part name=”sessionId” type=”xsd:string” />
    <part name=”resourcePath” type=”xsd:string” />
    <part name=”args” type=”xsd:anyType” />
    </message>
    <message name=”callResponse”>
    <part name=”callReturn” type=”ns2:Map” />
    </message>
    <message name=”multiCall”>
    <part name=”sessionId” type=”xsd:string” />
    <part name=”calls” type=”typens:FixedArray” />
    <part name=”options” type=”xsd:anyType” />
    </message>
    <message name=”multiCallResponse”>
    <part name=”multiCallReturn” type=”typens:FixedArray” />
    </message>
    <message name=”endSession”>
    <part name=”sessionId” type=”xsd:string” />
    </message>
    <message name=”endSessionResponse”>
    <part name=”endSessionReturn” type=”xsd:boolean” />
    </message>
    <message name=”login”>
    <part name=”username” type=”xsd:string” />
    <part name=”apiKey” type=”xsd:string” />
    </message>
    <message name=”loginResponse”>
    <part name=”loginReturn” type=”xsd:string” />
    </message>
    <message name=”resources”>
    <part name=”sessionId” type=”xsd:string” />
    </message>
    <message name=”resourcesResponse”>
    <part name=”resourcesReturn” type=”typens:FixedArray” />
    </message>
    <message name=”globalFaults”>
    <part name=”sessionId” type=”xsd:string” />
    </message>
    <message name=”globalFaultsResponse”>
    <part name=”globalFaultsReturn” type=”typens:FixedArray” />
    </message>
    <message name=”resourceFaults”>
    <part name=”resourceName” type=”xsd:string” />
    <part name=”sessionId” type=”xsd:string” />
    </message>
    <message name=”resourceFaultsResponse”>
    <part name=”resourceFaultsReturn” type=”typens:FixedArray” />
    </message>
    <message name=”startSession” />
    <message name=”startSessionResponse”>
    <part name=”startSessionReturn” type=”xsd:string” />
    </message>
    <portType name=”Mage_Api_Model_Server_HandlerPortType”>
    <operation name=”call”>
    <documentation>Call api functionality</documentation>
    <input message=”typens:call” />
    <output message=”typens:callResponse” />
    </operation>
    <operation name=”multiCall”>
    <documentation>Multiple calls of resource functionality</documentation>
    <input message=”typens:multiCall” />
    <output message=”typens:multiCallResponse” />
    </operation>
    <operation name=”endSession”>
    <documentation>End web service session</documentation>
    <input message=”typens:endSession” />
    <output message=”typens:endSessionResponse” />
    </operation>
    <operation name=”login”>
    <documentation>Login user and retrive session id</documentation>
    <input message=”typens:login” />
    <output message=”typens:loginResponse” />
    </operation>
    <operation name=”startSession”>
    <documentation>Start web service session</documentation>
    <input message=”typens:startSession” />
    <output message=”typens:startSessionResponse” />
    </operation>
    <operation name=”resources”>
    <documentation>List of available resources</documentation>
    <input message=”typens:resources” />
    <output message=”typens:resourcesResponse” />
    </operation>
    <operation name=”globalFaults”>
    <documentation>List of resource faults</documentation>
    <input message=”typens:globalFaults” />
    <output message=”typens:globalFaultsResponse” />
    </operation>
    <operation name=”resourceFaults”>
    <documentation>List of global faults</documentation>
    <input message=”typens:resourceFaults” />
    <output message=”typens:resourceFaultsResponse” />
    </operation>
    </portType>
    <binding name=”Mage_Api_Model_Server_HandlerBinding” type=”typens:Mage_Api_Model_Server_HandlerPortType”>
    <soap:binding style=”rpc” transport=”http://schemas.xmlsoap.org/soap/http” />
    <operation name=”call”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”multiCall”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”endSession”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”login”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”startSession”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”resources”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”globalFaults”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    <operation name=”resourceFaults”>
    <soap:operation soapAction=”urn:Mage_Api_Model_Server_HandlerAction” />
    <input>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </input>
    <output>
    <soap:body namespace=”urn:Magento” use=”encoded” encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” />
    </output>
    </operation>
    </binding>
    <service name=”MagentoService”>
    <port name=”Mage_Api_Model_Server_HandlerPort” binding=”typens:Mage_Api_Model_Server_HandlerBinding”>
    <soap:address location=”https://acceptance-nl.ms-mode.stone-it.com/index.php/api/soap/index/” />
    </port>
    </service>
    </definitions>

    #1914

    Andi
    Moderator

    Hi Frans,
    we are not able to get the WSDL properly from your posting.

    Can you please send the file to support(at)e2e.ch ?

    Regards,
    Andi

    #1920

    Andi
    Moderator

    Hi Frans,
    it turns out that this issue was caused by a bug in our WSDL importer.

    Ticket BUIL-4974 will fix the issue. The fix will be in our next builder and will be mentioned in the release notes then.

    For the time being, the WSDL import file can be amended manually to work around the issue.

    Best regards, Andi

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.