Client Proxy through WSDL

Hi,
I am creating a Client Proxy through WSDL Link in SE80 Transaction. I am getting an error 'NO Vendor Specified'. Please throw some light.
Thanks,
Mathivanan.G

I have tried that also same error.
This is my test WSDL File.
I am not able to paste the File contents i dont know Y
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://microsoft.com/webservices/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://microsoft.com/webservices/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://microsoft.com/webservices/">
      <s:element name="GetPrimeNumbers">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="1" maxOccurs="1" name="max" type="s:int" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="GetPrimeNumbersResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="GetPrimeNumbersResult" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="string" nillable="true" type="s:string" />
    </s:schema>
</wsdl:types>
<wsdl:message name="GetPrimeNumbersSoapIn">
    <wsdl:part name="parameters" element="tns:GetPrimeNumbers" />
</wsdl:message>
<wsdl:message name="GetPrimeNumbersSoapOut">
    <wsdl:part name="parameters" element="tns:GetPrimeNumbersResponse" />
</wsdl:message>
<wsdl:message name="GetPrimeNumbersHttpGetIn">
    <wsdl:part name="max" type="s:string" />
</wsdl:message>
<wsdl:message name="GetPrimeNumbersHttpGetOut">
    <wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:message name="GetPrimeNumbersHttpPostIn">
    <wsdl:part name="max" type="s:string" />
</wsdl:message>
<wsdl:message name="GetPrimeNumbersHttpPostOut">
    <wsdl:part name="Body" element="tns:string" />
</wsdl:message>
<wsdl:portType name="PrimeNumbersSoap">
    <wsdl:operation name="GetPrimeNumbers">
      <wsdl:input message="tns:GetPrimeNumbersSoapIn" />
      <wsdl:output message="tns:GetPrimeNumbersSoapOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="PrimeNumbersHttpGet">
    <wsdl:operation name="GetPrimeNumbers">
      <wsdl:input message="tns:GetPrimeNumbersHttpGetIn" />
      <wsdl:output message="tns:GetPrimeNumbersHttpGetOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:portType name="PrimeNumbersHttpPost">
    <wsdl:operation name="GetPrimeNumbers">
      <wsdl:input message="tns:GetPrimeNumbersHttpPostIn" />
      <wsdl:output message="tns:GetPrimeNumbersHttpPostOut" />
    </wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PrimeNumbersSoap" type="tns:PrimeNumbersSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <wsdl:operation name="GetPrimeNumbers">
      <soap:operation soapAction="http://microsoft.com/webservices/GetPrimeNumbers" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PrimeNumbersHttpGet" type="tns:PrimeNumbersHttpGet">
    <http:binding verb="GET" />
    <wsdl:operation name="GetPrimeNumbers">
      <http:operation location="/GetPrimeNumbers" />
      <wsdl:input>
        <http:urlEncoded />
      </wsdl:input>
      <wsdl:output>
        <mime:mimeXml part="Body" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:binding name="PrimeNumbersHttpPost" type="tns:PrimeNumbersHttpPost">
    <http:binding verb="POST" />
    <wsdl:operation name="GetPrimeNumbers">
      <http:operation location="/GetPrimeNumbers" />
      <wsdl:input>
        <mime:content type="application/x-www-form-urlencoded" />
      </wsdl:input>
      <wsdl:output>
        <mime:mimeXml part="Body" />
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
<wsdl:service name="PrimeNumbers">
    <wsdl:port name="PrimeNumbersSoap" binding="tns:PrimeNumbersSoap">
      <soap:address location="http://www50.brinkster.com/vbfacileinpt/np.asmx" />
    </wsdl:port>
    <wsdl:port name="PrimeNumbersHttpGet" binding="tns:PrimeNumbersHttpGet">
      <http:address location="http://www50.brinkster.com/vbfacileinpt/np.asmx" />
    </wsdl:port>
    <wsdl:port name="PrimeNumbersHttpPost" binding="tns:PrimeNumbersHttpPost">
      <http:address location="http://www50.brinkster.com/vbfacileinpt/np.asmx" />
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>
Edited by: Mathivanan G on May 13, 2009 1:14 PM

Similar Messages

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

Exception when creating ABAP client proxy using WSDL

Hi Experts,
I tried to create a client proxy on the CRM system for a web service URL (where the WSDL exists), in the transaction SE80.
When I tried creating this, i got exception as follows.
Exception occured in communication framework:error in HTTP framework:404 conn failed http://inld50054696a:8080/clearspace/rpc/rest?forumservice?wsdl
Please let me know, how to tackle this problem.
What are all the settings that needs to be done in this regard.
Regards
Lakshman

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

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

Error when create client proxy in ABAP

hi all
when I tried to create a client proxy through wsdl: http://www.webservicex.net/geoipservice.asmx?wsdl , I got and error message "Exception occurred in library handler", what's the really matter with this error ?
thanks very much!

You need to copy the WSDL file to a local file and edit it. The WSDL file contains non-SOAP bindings and that's what the generator is choking on. Use the 'Local file' option to generate the proxy class after editing the file.

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

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

Client proxy message not reaching to XI system

Hi
I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
Regards
Sowmya

Sowmya,
As you are not getting any message in SXMB_MONI, there can be following possibilities:
1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
How do you activate ABAP Proxies?
2. Make sure that in
SXMB_ADM --->integration engine config -
>change specific attributes....
The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
3. Make sure the queues are registered in Tx: SMQR.
Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

Creating client proxy for calling web service

Hello,
I like to call a WebServce from our vendor. The vendor provides me no WSDL document.
Question: Is it possible to create a client proxy without WSDL? I have just the SOAP Request/Response.
SAP ECC 6.0
SAP_BASIS 700 0010
Thank you very much in advance for any helpful answer.
Kind regards
Axel

Hi Axel,
I am working on a program to connect to a external web-service from SAP (R/3 enterprise 4.7) and while searching all the available stuff for this I got this method.
But, I am still facing some other issues and hence doesn't have the whole solution. You have to probably try it out from your side once and see if it helps.
Please refer the following blog.
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/847. [original link is broken] [original link is broken] [original link is broken]
it describes a method which is not at all using any WSDL file. Instead it uses the CL_HTTP_CLIENT class to pass a SOAP request to the web-service and then get the response.
Regards
Barada

Error at creating Client Proxy of external webservice (WSDL)

Hi Experts,
I try to create a Client Proxy Object out of an external webservice. Here is the WSDL URL:
[http://www.webservicex.net/CurrencyConvertor.asmx?wsdl]
I try to create it with this URL and then I get the error message
Not implemented
Exception of class CX_SIDL_INTERNAL_ERROR
I found two other threads with a similar problem:
cunsuming external webservice in ABAP
Problem while consuming external webservice
But there is no solution that worked for me. In the first thread it is mentioned, that the code between
<wsdl:binding name="XXXXHttpGet" type="tns:XXXHttpGet">
and it's closing brackets should be removed in a local file. I tried that and was able to create a client proxy object out of this local wsdl-file. But then I called the webservice with the folling coding for testing:
report z_currency_converter.
data: convert type ref to zzzco_currency_convertor_soap.
try.
    create object convert
exporting
    logical_port_name = 'Z_LP'
catch cx_ai_system_fault .
endtry.
   data: output type zzzconversion_rate_soap_out .
   data: input type zzzconversion_rate_soap_in .
   input-from_currency = 'EUR'.
   input-to_currency = 'USD'.
try.
call method convert->conversion_rate
exporting
    input = input
importing
    output = output
catch cx_ai_system_fault .
catch cx_ai_application_fault .
endtry.
write output-conversion_rate_result.
The same code worked fine in another system. In this "older" system could also create a client proxy, I think because it has a newer Support Pack version.
SAP says the following:
The problem is that this WSDL uses two bindings different from SOAP
binding which is not in conformance with Basic Profile 1.1 -
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#WSDLBINDINGS .
I looked in the document, but I do not know where the problem in the WSDL file exactly is. What have I to change? Or can somebody give me the URL of a free webservice, that you used for creating a client proxy with a new support pack standing? In the "old" system there is not yet the SOAMANAGER but in the one where it doesn't work.
I hope you have an idea.
Thanks a lot in advance!
Best Regards,
Ingmar

I think it is the problem of version.U need to ask SAP to release some patch levels to correct it.
Regards
Snehasish

Creation of client proxy for a WSDL with 2 port types??

Hi,
I am trying to consume an external web service from SAP - ECC6.0. The WSDL file has 2 porttype definitions - one for i/p and one for o/p
When I proceed with SE80 to create a client proxy, it asks me to select any one port type to generate the client proxy. If I select only the input port, it generates proxy for the input port alone.
In this scenario, how do I create proxies and configure logical ports, and call it from a single program to invoke the whole web servie with both i/p and o/p?
TIA,
Regards
Deepthi

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Creation of client proxy out of WSDL?

Hi ,
I need help in creating client proxy out of WSDL. It would be very helpful if someone lets me know the usage of performing this .I'm not much familiar with web services.
Regards,
Christina.

Hi,
right click on your package
create --> Enterprise Service / Web Service --> Proxy Object
-> URL/HTTP destination
-> Specify WSDL URL
Sometimes naming conficts occur.
Save and activate the proxy.
And then you have to call the proxy from a client application
regards

Create a Client Proxy for consume wsdl via https URL return a 110 HTTP code

Dear all.
I has new in this forum, and i have a problem when trie to create a client proxy from external WSDL, using https URL, system returns me a 110 http code. For others externs WSDL called via http don´t have any problem, and create client proxy perfect
Someone can help please.
best regards in advance.

Dear Anton I download de WSDL definition in a local file, but when I trie to use, the error persist.
If I test de URL via WebService navigation option, this work correctly, but if I put this URL thats begins with https, in se80--> create client proxy -->insert URL and then system returns the message HTTP error (return code 110, message "")
What it´s happen?.
Best regards in advance.
Juliá

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.

Client Proxy(WSDL file) via Se80

Hello
We have a client proxy created against a WSDL file (http/url) in SE80 and we are using it currently it.
Now the WSDL file is going to change a little. I want to use the same client proxy and only change the WSDL file with the new WSDL file? How can i acheive this?
I can create a new client proxy and associate WSDL file but i need to change a lot of place in code where we create instances of this abap proxy class.Hence i want to reuse the same client proxy while changing the WSDL file alone.
Any guidance or pointers will be greatly appreciated.
Thanks
Abishek

Hi Stuart,
Cool. This solves my issue. If I choose the "regenerate" button(see attached image) then I am prompted to enter a new WSDL URL or file.
Thanks!
Regards, Yashu

Client Proxy through WSDL

Similar Messages

Maybe you are looking for