External Service Generation - WSDL not accepted

Question

Hi,
I am struggeling to import my WSDL into the CAP SP 8 in the NW DevStudio.
A long time I received a an error "invalid WSDL" - no further comments.
After reading the SAPNote and comparing with working WSDLs I came up with that WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://com.bis/xi/esabox/demo" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://schemas.xmlsoap.org/soap/encoding/" name="CreateSAPOrderService" targetNamespace="http://com.bis/xi/esabox/demo">
     <types>
          <xsd:schema targetNamespace="http://com.bis/xi/esabox/demo">
               <xsd:complexType name="row">
                    <xsd:sequence>
                         <xsd:element name="p_idproduit" type="xsd:string"/>
                         <xsd:element name="p_nom" type="xsd:string"/>
                         <xsd:element name="p_type" type="xsd:string"/>
                         <xsd:element name="p_pu" type="xsd:string"/>
                         <xsd:element name="p_count" type="xsd:string"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:schema>
     </types>
     <message name="CreateSAPOrderRequest">
          <!--
          <part name="p_idproduit" type="xsd:int"/>
          <part name="p_nom" type="xsd:string"/>
          <part name="p_type" type="xsd:string"/>
          <part name="p_pu" type="xsd:float"/>
          <part name="p_count" type="xsd:int"/>
          -->
          <part name="row" type="tns:row"/>
     </message>
     <message name="CreateSAPOrderResponse">
          <part name="SAPOrderResponse" type="xsd:string"/>
     </message>
     <portType name="SAPOrder_PortType">
          <operation name="createSAPOrder">
               <input message="tns:CreateSAPOrderRequest"/>
               <output message="tns:CreateSAPOrderResponse"/>
          </operation>
     </portType>
     <binding name="SAPOrder_Binding" type="tns:SAPOrder_PortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="createSAPOrder">
               <soap:operation soapAction="createSAPOrder"/>
               <input>
                    <soap:body use="literal" namespace="http://com.bis/xi/esabox/demo"/>
               </input>
               <output>
                    <soap:body use="literal" namespace="http://com.bis/xi/esabox/demo"/>
               </output>
          </operation>
     </binding>
     <service name="Create_SAP_Order_Service">
          <documentation>WSDL File for CreateSAPOrderService</documentation>
          <port name="CreatSAPOrder_Port" binding="tns:SAPOrder_Binding">
               <soap:address location="http://iwdfvm2160:51000/XISOAPAdapter/MessageServlet?channel=:BSe_GREENATTITUDE_WS:CC_GREENATTITUDE_WS"/>
          </port>
     </service>
</definitions>
No I receive the error "Cannot convert MP Service Definition SAPOrder_PortType into MMR External Service. Reason: Program Error: Unexpected MP data. IStructure struct instance have to be of type IElement."
Well - for me that does not help a lot.
Has anyone an idea what I am doing wrong?
and BTW: I have the impression that CAF but also XI and VC heavily struggle to work with external WSDL. Does anyone know whether SAP is going to improve their products somewhen towards real-life applicability?
Thanks for any comment!!
Cheers.

Answer 1

Hi Ankit
I had managed to solve the problem with a workaround
1) I created an Proxy Project to wrap XI WSDL file in it
2) Then created EJB project to call wrapped XI web Service
   from ejb method. I then exposed this ejb method as web service
3) Finally created ear for ejb and deployed it on Web Application Server
4) now create External service project for the new wrapper web service it will get imported sucessfully and build and deploy also goes sucessfully
The difference this workaround does is that we do not have to consume XI webService directly which has little different structure and instead we consume wrapper web service which is generated out of an EJB and is available on JAVA stack your web service itself
CAF has no problem importing External services when they are hosted on web server JAVA itself
Hope my explanation convince you to go with this workaround
Thanks
Asif