Generate Client Proxy from a RPC-Style encoded WSDL

Hi Experts,
I was just trying to consume a RPC-Style encoded WSDL,
but the creation of the client proxy failed with the following error message:
Exception occurred in library handler     
Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/     
Does anyone know, if it's possible to consume a RPC-Style encoded Web Service?
Thanks in advance!

Hi Sandeep,
Could you try invoking clientgen [1] directly to see if this properly
consumes your WSDL?
Thanks,
Bruce
[1]
http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
Sandeep wrote:
>
Hi,
I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
as parameter and returns another XMLBean object. The web service works fine when
tested using the workshop's test browser but when i am trying to generate a client
proxy trough the workshop's test browser, it displays this warning:
Failed to generate client proxy from WSDL definition for this service
and does not generate the proxy.
I'll appreciate any thoughts on this.
Thanks
Sandeep

Similar Messages

  • Failed to generate client proxy from WSDL definition for this service

    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

    Hi Sandeep,
    Could you try invoking clientgen [1] directly to see if this properly
    consumes your WSDL?
    Thanks,
    Bruce
    [1]
    http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
    Sandeep wrote:
    >
    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

  • ABAP client proxy from WSDL

    I have 2 problems in creating abap client proxies using wsdl
    1.when i try to create client proxy by giving RPC style wsdl(generated by SAP itself for a RFC) the system throws an error and not allowing to create the proxy
    2.The client proxy which i have created for a wsdl(either SAP created document type/any wsdl from commercial websites) gives an error "No receiver could be found"
    could somebody please clarify and help me to solve the problem.
    Thanks in advance.
    Vasanth.

    Hi Vasanth,
    There are many threads and blogs on this topic.
    Choose the search Forum on the Forum page and select "All categories" in the Category field and enter your topic "ABAP client proxy from WSDL" in the search field.
    Rgds,
    Sam Raju

  • Error generating Client Proxy - object  missing in WSDL

    Hello,
    I have error while generating Client Proxy.
    I have WSDL and XSD in files. I get error message:
    object <message name="requestUPOMessage"> missing in WSDL
    Diagnosis
    In the WSDL document, the object
       "<portType name="GateServicePortType"> <operatio..."
    from the namespace
      "https://bramka.edeklaracje. mf.gov.pl/"
    links to the object
       "<message name="requestUPOMessage">"
    from the namespace
       "https://bramka.e-deklaracje.mf.gov.pl/"
    However, this last object does not exist in the WSDL document.
    WSDL FILE and XSD FILE: http://www.sendspace.com/filegroup/N8kSxPp5bhY2nVfcNBbAXg
    WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:ns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:gate="https://bramka.e-deklaracje.mf.gov.pl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="https://bramka.edeklaracje.
    mf.gov.pl/">
    <wsdl:types>
    <xs:schema attributeFormDefault="qualified" elementFormDefault="qualified"
    targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:include schemaLocation="GateService.xsd"/>
    </xs:schema>
    </wsdl:types>
    <wsdl:message name="sendDocumentWithAttachmentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachmentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOResponseMessage">
    <wsdl:part name="part1" element="ns:requestUPOResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentResponseMessage">
    <wsdl:part name="part1" element="ns:sendDocumentResponse">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendUnsignDocumentMessage">
    <wsdl:part name="part1" element="ns:sendUnsignDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentMessage">
    <wsdl:part name="part1" element="ns:sendDocument">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="requestUPOMessage">
    <wsdl:part name="part1" element="ns:requestUPO">
    </wsdl:part>
    </wsdl:message>
    <wsdl:message name="sendDocumentWithAttachmentMessage">
    <wsdl:part name="part1" element="ns:sendDocumentWithAttachment">
    </wsdl:part>
    </wsdl:message>
    <wsdl:portType name="GateServicePortType">
    <wsdl:operation name="sendDocument">
    <wsdl:input message="gate:sendDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <wsdl:input message="gate:sendUnsignDocumentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendUnsignDocumentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <wsdl:input message="gate:sendDocumentWithAttachmentMessage">
    </wsdl:input>
    <wsdl:output message="gate:sendDocumentWithAttachmentResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <wsdl:input message="gate:requestUPOMessage">
    </wsdl:input>
    <wsdl:output message="gate:requestUPOResponseMessage">
    </wsdl:output>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="GateServiceSOAP12Binding" type="gate:GateServicePortType">
    <soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap12:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap12:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap12:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap12:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap12:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:binding name="GateServiceSOAP11Binding" type="gate:GateServicePortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendDocument">
    <soap:operation soapAction="urn:sendDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendUnsignDocument">
    <soap:operation soapAction="urn:sendUnsignDocument" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="sendDocumentWithAttachment">
    <soap:operation soapAction="urn:sendDocumentWithAttachment" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="requestUPO">
    <soap:operation soapAction="urn:requestUPO" style="document"/>
    <wsdl:input>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal" namespace="https://bramka.e-deklaracje.mf.gov.pl/"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="GateService">
    <wsdl:port name="GateServiceSOAP12port" binding="gate:GateServiceSOAP12Binding">
    <soap12:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    <wsdl:port name="GateServiceSOAP11port" binding="gate:GateServiceSOAP11Binding">
    <soap:address location="https://test-bramka.edeklaracje.gov.pl/uslugi/dokumenty/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    XSD
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="https://bramka.edeklaracje.
    mf.gov.pl/xsd" targetNamespace="https://bramka.e-deklaracje.mf.gov.pl/xsd"
    elementFormDefault="qualified" attributeFormDefault="qualified">
    <xs:element name="sendDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocument">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendUnsignDocumentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachment">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="attachment" type="xs:base64Binary" minOccurs="0"/>
    <xs:element name="document" type="xs:base64Binary"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="sendDocumentWithAttachmentResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPO">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="refId" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="requestUPOResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="upo" type="xs:string" minOccurs="0"/>
    <xs:element name="status" type="xs:int"/>
    <xs:element name="statusOpis" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    Maybe someone know what is wrong in wsdl file and how to correct this?

    Hi Marcus,
    Did you fix the problem?
    I'm asking because I'm dealing with the same problem! I tried to generate a Proxy object from a WSDL document and I can't... I always receive the error "Cannot generate proxy (object  missing in WSDL, see long text)". I have checked on the service.sap.com and I found a xls document with all unsupported WSDL elements and one of them is the "part name=" and I have it in my WSDL! I don't know how to workaround this issue, can you help me please?
    Thanks in advance,
    Ricardo.

  • Bad Request OSB Local Proxy to Business RPC Style

    Hello,
    I have a problem calling a web service rpc style base from a local proxy.
    Here is the situation.
    I have 1 Bussiness Service RPC style base (wsdl base).
    I have 1 Proxy Service (Local Transport) Lets call this one LPS1.
    I have 1 Proxy Service (Local Transport) Lets call it LPS2.
    When I call BS from osb console, the response is OK.
    When I call from osbconsole LPS1 to BS through a rountin node the response is OK. (I also tried Service Callout).
    BUT, When I call from osbconsole LPS2 to LPS1 to BS, I got BAD REQUEST...
    I have already tried everythin, but I could not I get the solution.
    Thus,
    call BS = OK
    call LPS1 -> BS = OK.
    call LPS2 -> LPS1 -> BS = BAD REQUEST.
    I have compared both outbound variables and there are the same.
    Thanks in advance.
    Gustavo.

    Swapnil,
    Publish call will be blocking if QoS is set as Exactly-Once.
    If QoS is Best-Effort and target endpoint is a one-way proxy service then it is a blocking call (source proxy waits for target proxy message flow completion) and if QoS is Best-Effort and target endpoint is a request-response proxy service then control returns back to source proxy as soon as Request pipeline of target proxy message flow completes.
    Regards,
    Anuj

  • Client proxy from user exit

    I am invoking a client proxy from user exit (user exit is invoked in update task). Is there any red flags I need to be aware of.
    Proxy takes a while to execute and till that time, My original document does not get updated.

    Hi Kris,
    If it gives u Timeout error then only data will not be posted and it will  be an issue.
    If data posted from proxy then check in SXMB_MONI in Ecc side.
    Regards,
    Phani

  • Error  while generating client proxy

    Hi All,
    I have got a WSDL file for which I am generating the client proxy. It is giving me a dump saying that, memory is not sufficient while generating the proxy.
    I have also contacted the basis team, even after increasing the memory... we are facing the same issue. Can anyone suggest any solution or SAP Note if there are any???
    Thanks in advance.
    Bhargava.

    Hi,
    Please find the dump details below:
    ST22 DUMP:
    Short text
        No storage space available for FORM stack.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
        Try to find out (e.g. by targetted data selection) whether the
        transaction will run with less main memory.
        If there is a temporary bottleneck, execute the transaction again.
        If the error persists, ask your system administrator to check the
        following profile parameters:
        o  ztta/roll_area            (1.000.000 - 15.000.000)
               Classic roll area per user and internal mode
               usual amount of roll area per user and internal mode
        o  ztta/roll_extension       (10.000.000 - 500.000.000)
               Amount of memory per user in extended memory (EM)
        o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
               Amount of memory (malloc) for all users of an application
               server. If several background processes are running on
               one server, temporary bottlenecks may occur.
               Of course, the amount of memory (in bytes) must also be
               available on the machine (main memory or file system swap).
               Caution:
               The operating system must be set up so that there is also
               enough memory for each process. Usually, the maximum address
               space is too small.
               Ask your hardware manufacturer or your competence center
               about this.
               In this case, consult your hardware vendor
        abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each dialog process.
        Parameters for background processes:
        abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
               Restriction of memory allocated to the heap with malloc
               for each background process.
        Other memory-relevant parameters are:
        em/initial_size_MB:         (35-1200)
               Extended memory area from which all users of an
               application server can satisfy their memory requirement
    Error analysis
        You attempted to extend a stack, but the required storage spac
        not available.
        Storage request..............: 8450048 bytes.
    How to correct the error
        Please check whether uncontrolled recursive calls caused this
        runtime error.
        Try to decide by analysis whether this request is
        reasonable or whether there is a program error. You should pay
        particular attention to the internal table entries listed belo
    System environment
        SAP-Release 701
        Application server... "dcr"
        Network address...... "10.1.105.112"
        Operating system..... "AIX"
        Release.............. "6.1"
        Hardware type........ "00C834224C00"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 4

  • Problem Calling a Client Proxy from ABAP which is based on an extension

    I'm trying to create an Asset in Salesforce from SAP using ABAP.
    I have exported the enterprise WSDL from Salesforce, generated a client proxy and have coded the login call and passed the session id to the create call.
    The problem I am having is the create method references sobject however asset is an extension of this.
                <complexType name="Asset">
                    <complexContent>
                        <extension base="ens:sObject">
                            <sequence>
                            <element name="Account" nillable="true" minOccurs="0" type="ens:Account"/>
                            <element name="AccountId" nillable="true" minOccurs="0" type="tns:ID"/>
                            <-- many more fields here -->
                            </sequence>
                        </extension>
                    </complexContent>
                </complexType>
    I need to pass something like this (tested and working using SOAPUI)
             <urn:sObjects xsi:type="urn:Asset"
                       xmlns:ns3="urn:sobject.enterprise.soap.sforce.com">  
                   <urn:AccountId>001A000000HoyKZ</urn:AccountId>
                   <urn:Name>JWSOAPTEST Asset3</urn:Name>    
                            <-- many more fields here -->
            </urn:sObjects>
    I tried modifying the WSDL so sobject referrs to Asset
                <!-- Create Message Types -->
                <element name="create">
                    <complexType>
                        <sequence>
                            <!-- element name="sObjects" type="ens:sObject" minOccurs="0" maxOccurs="unbounded" -->
                           <element name="sObjects" type="ens:Asset" minOccurs="0" maxOccurs="unbounded"/>
                        </sequence>
                    </complexType>
                </element>
                <element name="createResponse">
                    <complexType>
                        <sequence>
                            <element name="result" type="tns:SaveResult" minOccurs="0" maxOccurs="unbounded"/>
                        </sequence>
                    </complexType>
                </element>
    However other types it referred to weren't populated.
    The other approache may be to manually populate the xml similar to what I had to do in the header (this link gives a good overview on this Consume web service in ABAP proxy with SOAP header )
    Any recommendations or advice would be appreciated.
      Ideally some sample code if someone has done this or a recommendation on how to modify the WSDL.
    Regards,
    John

    Hi John,
    Calling SFDC.com from PI, is detailed out here. probably will give some tips:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50a76cfa-4966-2d10-aba7-da496d9b5bcf
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/802f8d03-9282-2d10-52b4-f9446e077099
    Regards, Moorthy

  • ABAP Client Proxy from ECC 6.0 to XI message irregular recieving

    Hi Gurus
    Any one has come across issue whereby the ECC 6 system trigger ABAP Client proxy to SAP PI 7.0. The first time the PI is able to recieve it in the SXI_MONITOR. But subsequent trigger from the ECC 6.0 system the SAP ABAP program to trigger the Client Proxy, the PI seem to lost connectivity and did not recieve any message. This is pretty strange and hopefully someone in SDN and enlighten me.
    Thanks
    Regards
    On behalf of malcolm

    Hi Santosh
    I went to SMQR and register the queue, but it still did not reflect the locked queue when i trigger the ECC 6 to SAP PI 7.0. The green flag - schedule still appear in the SXMB_MONI queue. But i am quite puzzle as why the ABAP client proxy after sending message the first time and second time, the third time it stuck? And also it is not practical to everytime go to the SMQ1 or SMQ2 to unlock the queue. I don't think it a good solution for solving my problem, it is just a temporary solution.

  • Namespace Error when generating Client Proxy for Java Web Service

    Hi.Experts:
        When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
        The error like this:
        "Incorrect value: Unknown Namespace http://sql.java
        Exception of class CX_SLIB "
       I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
    Best Regards
    Martin Xie

    Hi Martin
    I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
    Maybe my version is different.
    You say that you can select the file ou url.
    Did you select the file or url?
    If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
    If was url, access this url, copy the xml and same in one file, then select this file in the step above.
    I don't know if works, its only a suggestion.
    regards
    Marcos

  • Error while creating Client Proxy from SE80

    Hi all,
    I am trying to create Client Proxy with WSDL through SE80. There is no involvement of XI to create the Proxy.
    I am using the option 'Local file' and uploading the wsdl file.
    But I am getting the following errors.
    "Proxy-Generierung: Fehler aufgetreten"
    "Exception occurred in library handler"
    "Illegal syntax: Element header has invalid enhancement attribute
    http://schemas.xmlsoap.org/wsdl/:required"
    If any one could understand them and worked in a similar scenario, pls help me out.
    regards,
    teja.

    hi,
    you might want to post the WSDL in question for us to have a look at.
    but actually, the error message tells a lot:
    http://schemas.xmlsoap.org/wsdl/:required
    the second colon(, the one between wsdl/ and required, makes this expression an illegal one in any kind of a URI-like meaning (namespace, ref-URL, ...)
    anton

  • Generating Client Proxy

    Hi all,
    I am trying to create an Enterprise Service Client Proxy in TA SE80.
    But creation of the proxy fails with the error message SPRX038
    WSDL-Error (<extension> is not supported).
    Anyone got an idea?
    Thanks and Regards
    D

    Hi,
    Few of the <xsd> types are not supported by SAP and if your wsdl contains those xsd type then proxy generation will fail.
    Please post wsdl if possible to see what the problem is.
    In this case <extension> tag is problem (it support only simple content type). Tell us which SAP BASI SP level is?
    Also refer to this article for supported XML tags by SAP.
    NW 7.1: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a9a425-1769-2a10-9196-bd8eeed72e4c
    NW 2004/s: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/708cff46-1569-2a10-40bf-90694e16cb95
    Regards,
    Gourav

  • How to generate a soapFault from jax-rpc hander

    Hello,
    I'm building a custom authentication jax-rpc handler (OAS 10.1.3.1) that is supposed to make the service to return a fault if some conditions are not met.
    Here is what we need to return:
    <Fault><faultcode>invalidIP</faultcode><faultstring>IP is not known</faultstring><faultactor></faultactor></Fault>
    I tried to throw a SOAPFaultException, but all the is returned back is the original SOAP request.
    How should it be implemented?
    if ( !res ) {
    Detail detail = null;
    try{
    detail = SOAPFactory.newInstance().createDetail();
    }catch(SOAPException ex){
    ex.printStackTrace();
    throw new javax.xml.rpc.soap.SOAPFaultException(
    new javax.xml.namespace.QName("env.Server"),
    "IP is not known", "NO ACTOR", detail);
    }

    Hello ,
    I think you need to use the Work item Change set
    cube of TFS .You need to go through the below page
    http://msdn.microsoft.com/en-us/library/ms244678.aspx
    Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

  • Got error when trying to generate Java proxy jar file for webservice

    Hi,
    I am having a warning message when trying to generate java proxy jar file on weblogic8.1
    webservice test web app, the message is as follows:
    "Warning Failed to generate client proxy from WSDL definition for this service.
    Prescription Please verify the <types> section of the WSDL."
    in the mean time, on weblogic starting terminal, I saw the following exceptions,
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils"
    Can anybody help me about this issue? I attached WSDL file, also United Airlines
    got an enterprise weblogic license deal with BEA, any help will be highly appreciated.
    Thanks!!!
    Naichen
    [ModifyPNRWSContract.wsdl]

    Hi Naichen,
    I was able to successfully run both the autotype and clientgen Ant task, on the
    WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
    Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
    to try with that version.
    Regards,
    Mike Wooten
    "Naichen Liu" <[email protected]> wrote:
    >
    >
    >
    Hi,
    I am having a warning message when trying to generate java proxy jar
    file on weblogic8.1
    webservice test web app, the message is as follows:
    "Warning Failed to generate client proxy from WSDL definition for this
    service.
    Prescription Please verify the <types> section of the WSDL."
    in the mean time, on weblogic starting terminal, I saw the following
    exceptions,
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
    symbol : class FacetUtils
    location: package binding
    weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
    ^
    C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
    t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
    symbol
    symbol : class FacetUtils"
    Can anybody help me about this issue? I attached WSDL file, also United
    Airlines
    got an enterprise weblogic license deal with BEA, any help will be highly
    appreciated.
    Thanks!!!
    Naichen

  • Not getting response from Client Proxy

    Hi,
    We are developing a scenario - File->PI->Proxy using ABAP Proxies.We are posting a file thru PI 7.0 to R/3 .In R/3 the server proxy(Inbound Asynchronous) will receive the message and BAPI will be called. The response from the BAPI will be reaching the server proxy and passed to the client proxy(Outbound Asynchronous).
       Server Proxy(request) --> BAPI --> Server Proxy(response) --> Client Proxy(response)
    The response from the client proxy has to be send to PI and a file will be generated as the output.
    Can anyone provide me suggestions to call client proxy from a server proxy by passing the response message to client proxy???
    Thanks in advance.
    Regards,
    Dibyajyoti

    Hi,
    I hope, you are done till the Implementation of Server Proxy, where you are calling a Bapi and passing the Input variables the Interface received and BAPI is giving a response back.
    Now your question, how to send the response back Asynchronously.
    I think, you have to do the same, what you do for a client proxy  and at last  call the method EXECUTE_ASYNCHRONOUS before the Final Commit Staement. I think this should work.
    But using Synchronous Interface in such cases is always a handy and easier option.
    Regards,
    Subhendu

Maybe you are looking for

  • New mac book pro setup questions

    I am about to get a macbook pro dual 2.6 4gb ram 320gb 7200 hard drive. I will be putting fc studio on it and was wondering how to arrange and use external hard drives. I am not a big fan on letting the internal hard drives to all the work, so I have

  • How can i use month dynamically in the report?

    Hi Xperts, i have requirment that i need to display the data on the report output only for one month. and it will dynamically change in every month with out using any selections in the selection screen. i found that i have to use customer exits for i

  • I have not been able to go to links when in Firefox. When I open the same page in Internet Explorer it works.

    Since I upgraded to the latest Firefox a few days ago I have not been able to access certain links. When I switch to Internet Explore those link work.

  • Captivate 7 and Audition CC on MacOSX 10.8.4

    Hi, i record a video demo with CP7. If I export the audio to Audition CC, the application started, but the audio from the demo isn't avaliable in Audition. Any ideas, what's wrong? Thank you Andreas

  • Remove breadcrumb navigation Tree.

    Hi Experts, How can i remove the breadcrumb navigation tree that appears just below the top level navigation fro ESS. I have seena  few blogs af dound that the changea are done at the coding level. Here we are using the standard ESS application and m