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.

Similar Messages

Error generating client-specific objects

Dear all,
while generating environment in maintain operating concern i am getting following error
Message no. KE007
Diagnosis
     The system automatically adjusted operating concern PAPL, or the
     environment of operating concern PAPL was regenerated. An error occurred
     while the system was generating client-specific objects in client 600.
System Response
     Operating concern PAPL cannot be used in client 600.
Procedure
     If this message is contained in the generation log, see the messages
     that occurred before it for details about the error.
     If this message appeared during the automatic adjustment, try to
     generate the environment using the Customizing transaction KEA0.
Activate data structures, generate environment
so i could not generate the environment in development server
kindly help me ..
Thanks and regards
vijay

Dear paul,
Thanks for you reply
Actually the problem is when op.concern was generated in dev.server it was transported to test and production server,but while transporting some request from development my client got dump in development server and so operating concern was changed to transport the requests.Also in old operating concern some characteristics and value fields were added and deleted by user .Now when trying to activate environment (client specific part) it gives above error message.
also we have got reply from sap which is as under:
1)Thanks for the log in details. I was logged in to your system and checked the issue. I found few inconsistencies in the system. Please let me know if you have deleted any characteristic or value fields or if you have done any COPA transports recently.
2)Thanks for the reply, we have changed and deleted characteristicsand value fields. Since we have changed our operating concern PAPL TO PAP1 and then assigned to controlling area PAPL which is not transported
to production server then again we have changed as usual PAPL so we are facing this activation problem .please guide us to solve this problem as early as possible
3)) I am not sure if I can help you resolving the issue as this is purely an inconsistency created by user action. These kinds of issues can be solved only by our remote consulting colleagues. However if you want to restore the old settings you can transport the operating concern through KE3I from your quality or production where the system is working fine.
In test and production my operating concern is working fine ,is it possible to transport request from test or production to development ?
also kindly suggest any other solutions
Thanks and Regards
vijay

Cannot generate proxy (object missing in WSDL)

Hi folks,
Once again, my apology for this thread isnt 100% XI forum related. But, continuing with this issue
As you can see on my earlier post
Consuming an external web service with WAS 6.40
Im trying to consume an external web service. Following Michals suggestion I have checked the WSDL in debug mode and I found some irregularities on it. It seams this WSDL doesnt describe the whole interface correctly. Looking to Diagnosis, I see an object "<message name="listaCodSig0Request"> <part name..." that is linked to an empty object, or either, doesnt exist in the WSDL document!!!
ABAP proxy generation expects that all directly and indirectly referenced objects are in the WSDL document. Therefore, no proxy can be generated for this WSDL and the system displays an error message.
It seams that this web service was developed through messages with several parts. Searching in http://service.sap.com I found a document XSDandWSDL_XI30SP11.xls with supported XML schema and WSDL. In this doc I can see that messages with several parts are not supported!!!
I would like to know how can I workaround this issue. Is it possible replace these elements part name= with other supported elements in the WSDL document and without changes on the web service? Im asking this because this external web service are working well with other third party client applications and is not supposed perform any changes on that.
I tried to replace part name= to part element= , but it doesnt work! Proxy generation terminated: WSDL error (object part without name)
Anyone knows which elements I should use in replace of these unsupported elements and which procedures I need to taking into account?
Thanks in advance,
Ricardo.

Hey Ricardo,
First of all, when I tried to save your wsdl in XMLSpy, it complained about the empty soapaction declaration in the <operation> tag. I had to remove the line
<soap:operation soapAction="" style="rpc" />
in order to make it work in XMLSpy. It would be a good idea to check that out with the developers of the wsdl.
Anyway, after I removed that tag, I start comparing your wsdl to a common Message Interface wsdl generated by XI. By doing that, I have found out that the <part> element in XI has a name and also refers to an existing element, which was previously defined in the <schema> group.
I've made some modifications, you could try it, but I have found an issue about this approach. With your wsdl, the soap request message has a <listaCodSig> tag with namespace "http://db_cml_alcor_mgb/Moradas_Edificios.xsd", and inside it, you have a <pDesignLocal> tag with no namespace defined.
If you use the modificated wsdl below, both <listaCodSig> and <pDesignLocal> tags have namespace as "http://db_cml_alcor_mgb/Moradas_Edificios.xsd", and I think that'll cause issues in your server application. But you can try it out, playing with the wsdls, if you can remove the definition there.
The modificated wsdl is below (changed parts in bold).
<?xml version="1.0" encoding="utf-8"?>


<definitions
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://alcor.cm-lisboa.net:7777/CML-SRUs-context-root/Moradas_Edificios.wsdl"
xmlns:ns1="http://db_cml_alcor_mgb/Moradas_Edificios.xsd"
name="Moradas_Edificios"
targetNamespace="http://alcor.cm-lisboa.net:7777/CML-SRUs-context-root/Moradas_Edificios.wsdl">
<types>
<schema
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
targetNamespace="http://db_cml_alcor_mgb/Moradas_Edificios.xsd">
<element name="pDesignLocal" type="xsd:string"/>
<element name="return" type="ns1:db_cml_alcor_mgb_TabMoradaEdif"/>
<complexType name="db_cml_alcor_mgb_TabMoradaEdif"
jdev:packageName="db_cml_alcor_mgb"
xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="array"
type="ns1:ArrayOfdb_cml_alcor_mgb_MoradaEdifUser"/>
</all>
</complexType>
<complexType name="db_cml_alcor_mgb_MoradaEdifUser"
jdev:packageName="db_cml_alcor_mgb"
xmlns:jdev="http://xmlns.oracle.com/jdeveloper/webservices">
<all>
<element name="codSig" type="string"/>
<element name="desigLocal" type="string"/>
<element name="codLocal" type="string"/>
<element name="nrPol" type="string"/>
<element name="nome" type="string"/>
<element name="nrObraConstrucao" type="string"/>
<element name="freguesia" type="string"/>
<element name="areaGestao" type="string"/>
</all>
</complexType>
<complexType name="ArrayOfdb_cml_alcor_mgb_MoradaEdifUser"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<complexContent>
<restriction base="SOAP-ENC:Array">
<attribute ref="SOAP-ENC:arrayType" wsdl:arrayType="ns1:db_cml_alcor_mgb_MoradaEdifUser[]"/>
</restriction>
</complexContent>
</complexType>
</schema>
</types>
<message name="listaCodSig0Request">
<part name="pDesigLocal" element="ns1:pDesignLocal"/>
</message>
<message name="listaCodSig0Response">
<part name="return" element="ns1:return"/>
</message>
<portType name="Moradas_EdificiosPortType">
<operation name="listaCodSig">
<input name="listaCodSig0Request" message="tns:listaCodSig0Request"/>
<output name="listaCodSig0Response" message="tns:listaCodSig0Response"/>
</operation>
</portType>
<binding name="Moradas_EdificiosBinding" type="tns:Moradas_EdificiosPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="listaCodSig">
<input name="listaCodSig0Request">
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="Moradas_Edificios"/>
</input>
<output name="listaCodSig0Response">
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="Moradas_Edificios"/>
</output>
</operation>
</binding>
<service name="Moradas_Edificios">
<port name="Moradas_EdificiosPort" binding="tns:Moradas_EdificiosBinding">
<soap:address location="http://alcor.cm-lisboa.net:7777/CML-SRUs-context-root/Moradas_Edificios"/>
</port>
</service>
</definitions>
Regards,
Henrique.

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 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

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 While Generating the Proxy Objects

Hi All,
While Generating the Proxy Obects in SPROXY at SAP R/3 side,
Iam getting this Error
http://img169.imageshack.us/img169/5752/proxylm0.jpg
Can any one Occured this type of Error
Regards
Suman

Hi PT,
Now the Strange Issue came,
While generating the proxy objects i got that above mentioned error
After that i have run the 3 report programs according to the Ramesh Suggession
Now if i goto SPROXY means it is saying that No Conection to Integration Builder .
I have checked the RFC Destination created in SM59 of SAP R/3 of Type H.It is fine
What more i have to check
First of all when ever i open the Sropxy, every time User & pwd is requesting
Can you please through a light where to check
Regards
Suman

Proxy Object for external WSDL--Not using XI

Dear Collegues,
URL OF web service: http://www.nanonull.com/TimeService/TimeService.asmx
I am trying to create proxy object from se80->enterprise services->create proxy
then is selecting url/http and giving the above address(url).
i get this error.
Message no. SPRX090
If you want to generate a proxy for an external WSDL document (for example, by specifying a URL), check that the proxy settings of the system are correct (transaction sicf - Client - Proxy Settings).[/b
it says something should be correct in SICF,say any one provide some pointers for this.I am not using XI.
Regards
chandra

Hi,
I know this issue is logged some time back.
Is this Issue fixed for you?
Can you please let us know the SICF Config settings that you used for fixing this Issue?
Thanks and Regards,
Nagendra

Errors generating client stubs for web services

Hello,
We are having issues trying to generate client stubs from the Unifier wsdl document (mainservice.wsdl). I see this was generated using Axis 1.4 (2006). I normally use Apache CXF but it complains due to the use of RPC/encoding. I tried Axis2 but it complains about "SchemaCompilationException: can not find type {http://schemas.xmlsoap.org/soap/encoding/}Array from the parent schema". I am wondering if we need to use Axis 1.4?
If you have successfully generated client stubs from the wsdl documents please let me know which method was successful for you.
We have Unifier R9.12 installed.
Thank you
Rudy

I found more notes on what I had to do:
- the process above created package names like java.oracle_e1_bssv_jp010000
- we need to rename these to be proper package names.
- refresh the eclipse project so you see these folders
- select the package, right click, refactor, rename
- rename these to be like oracle.e1.bssv.jp010000 (remove the java. and replace _ with .)
- there will probably be a bunch of errors in individual java files you will need to fix.
- they are very easy, it should be a matter of just deleting the imports, these are not needed because they are in the same package.

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 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

SPRX038 error while creatign proxy object from WSDL

Hi,
I am trying to create SE80 --> create Proxy Object using WSDL file..
when i am trying to import WSDL file, it is throwing error.
It says "Proxy generation terminated: WSDL error (<#text> not supported)"
Message no. SPRX038.
when i checked my WSDL there is not <#text> or either any'text' is there in WSDL.
Please help me to resolve the problem...
please find the error...
Proxy generation terminated: WSDL error (<#text> not supported)
Message no. SPRX038
Background
During proxy generation, an interface description in WSDL format is fetched from the Integration Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
==> Display Query
==> Display WSDL Document
Diagnosis
The language element
"<#text>"
was used in the WSDL document.
This language element is not supported by ABAP proxy generation.

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

Error in activating proxy object

hi
when i m trying to activate my proxy objects in CLIENT PROXY scenario in the ECC , the following error message is being prompted :
Erro in object editing :
"SAP object CLAS CO_PRXY_MI cannot be assigned to
package ZXIPACKAGE:
A package has been created in ECC by the name of zxipackage .
Pl help to rectify the problem
rgds
shazia

Hi,
You should assign it to Z-package ie.e Customized one not SAP package
Use a prefix of Z when doing the generation and you can use your own development class. you are trying to create objects in the SAP namespace.
The Proxy object should have to be in non SAP package only, if its customized.
As while activating the ABAP proxy internally Class and verious methods as well as some data typs get creaetd which are to be assigned it Z-package.
refer below link
Tips for Generating ABAP Proxies
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/f49b21674e8c44940bb3beafd83d5c/frameset.htm
thanks
Swarup

Error in client proxy generation

Hi experts,
 I am trying to consume a web-service from an ABAP progam, to do this I create an Enterprise Service Client Proxy. But creation of the proxy fails with the error message
"Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/ .
 For client confidentiality issues I cannot put the wsdl file or its content on the thread but I can provide certain details of the code which you might wish to see.
Also my wsdl contains messages with miltiple parts.Is this also a trouble while generating the proxies in ABAP ?
Are these two problems related?
Can I find a link precisely which can provide a kind of checklist to see that these steps have to be followed or these conditions have to be met by wsdl for generation of client proxies in ABAP?
Any pointers will be useful.
Thanks and Regds
Abhishek

Hi Anton,
 I will provide you some piece of the file which might help you in analysing the problem....
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://www.abc.com"
xmlns:s1="http://www.abc.com/AbstractTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://www.abc.com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
 <s:schema targetNamespace="http://www.abc.com/AbstractTypes">
 <s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
 <s:complexType name="StringArray">
 <s:complexContent mixed="false">
 <s:restriction base="soapenc:Array">
 <s:sequence>
 <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string" />
 </s:sequence>
 </s:restriction>
 </s:complexContent>
 </s:complexType>
 </s:schema>
Similarly the WSDL has messages with multiple parts like:
<wsdl:message name="GetReleasedGenericDrawing2DHttpGetIn">
 <wsdl:part name="DocumentNo" type="s:string" />
 <wsdl:part name="SheetNo" type="s:string" />
 <wsdl:part name="ClassName" type="s:string" />
</wsdl:message>
If you need some ther details from the file please let me know. I have cross checked that it is using a Document/literal style so it should not be a problem.
I have gone through the SAP note (944029) for the list some forbidden keywords which were a problem prior to release of SP 16 .We dont have even that problem.
This thing is very new to me ....please let me know if you wnat some other detail for analysis.
Regads
Abhishek

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

Error generating Client Proxy - object missing in WSDL

Similar Messages

Maybe you are looking for