WSDL generated through SOAMANAGER cannot be loaded into flex

[Former Member]

Guys,

I'm having a problem here where I use soamanager to generate the WSDL for a webservice named: ztestpg_ws.

for some reason, Adobe Flex cannot load it. Any ideas at all????

Here is the WSDL:

  <?xml version="1.0" encoding="utf-8" ?> 
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <wsdl:documentation>
  <sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" /> 
  </wsdl:documentation>
  <wsp:UsingPolicy wsdl:required="true" /> 
- <wsp:Policy wsu:Id="BN_ztestpg_ws">
- <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
- <wsp:All>
- <sp:TransportBinding>
- <wsp:Policy>
- <sp:TransportToken>
- <wsp:Policy>
  <sp:HttpsToken /> 
  </wsp:Policy>
  </sp:TransportToken>
- <sp:AlgorithmSuite>
- <wsp:Policy>
  <sp:TripleDesRsa15 /> 
  </wsp:Policy>
  </sp:AlgorithmSuite>
- <sp:Layout>
- <wsp:Policy>
  <sp:Strict /> 
  </wsp:Policy>
  </sp:Layout>
  </wsp:Policy>
  </sp:TransportBinding>
  </wsp:All>
  </wsp:ExactlyOne>
  <saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" /> 
  </wsp:Policy>
- <wsp:Policy wsu:Id="IF_ztestpg_ws">
- <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">
  <sapsession:enableSession>false</sapsession:enableSession> 
  </sapsession:Session>
  <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" /> 
  </wsp:Policy>
- <wsp:Policy wsu:Id="OP_Ztestpg">
  <sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit> 
  <sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking> 
  <saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required> 
  <saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM> 
  </wsp:Policy>
- <wsdl:types>
- <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
- <xsd:element name="Ztestpg">
- <xsd:complexType>
  <xsd:sequence /> 
  </xsd:complexType>
  </xsd:element>
- <xsd:element name="ZtestpgResponse">
- <xsd:complexType>
- <xsd:sequence>
  <xsd:element name="Rc" type="xsd:int" /> 
  </xsd:sequence>
  </xsd:complexType>
  </xsd:element>
  </xsd:schema>
  </wsdl:types>
- <wsdl:message name="Ztestpg">
  <wsdl:part name="parameters" element="tns:Ztestpg" /> 
  </wsdl:message>
- <wsdl:message name="ZtestpgResponse">
  <wsdl:part name="parameter" element="tns:ZtestpgResponse" /> 
  </wsdl:message>
- <wsdl:portType name="ztestpg_ws">
- <wsp:Policy>
  <wsp:PolicyReference URI="#IF_ztestpg_ws" /> 
  </wsp:Policy>
- <wsdl:operation name="Ztestpg">
- <wsp:Policy>
  <wsp:PolicyReference URI="#OP_Ztestpg" /> 
  </wsp:Policy>
  <wsdl:input message="tns:Ztestpg" /> 
  <wsdl:output message="tns:ZtestpgResponse" /> 
  </wsdl:operation>
  </wsdl:portType>
- <wsdl:binding name="ztestpg_ws" type="tns:ztestpg_ws">
- <wsp:Policy>
  <wsp:PolicyReference URI="#BN_ztestpg_ws" /> 
  </wsp:Policy>
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
- <wsdl:operation name="Ztestpg">
  <soap:operation soapAction="" style="document" /> 
- <wsdl:input>
  <soap:body use="literal" /> 
  </wsdl:input>
- <wsdl:output>
  <soap:body use="literal" /> 
  </wsdl:output>
  </wsdl:operation>
  </wsdl:binding>
- <wsdl:service name="service">
- <wsdl:port name="ztestpg_ws" binding="tns:ztestpg_ws">
  <soap:address location="http://jq03a010.esc.win.colpal.com:8035/sap/bc/srt/rfc/sap/ztestpg_ws/321/ztestpg_ws/ztestpg_ws" /> 
  </wsdl:port>
  </wsdl:service>
  </wsdl:definitions>

[manish_bhalla2 · Accepted solution]

Hi Yves,

Can you load the wsdl into an external app like XMLSPY without errors? We are facing a problem with the WSDL generated in the SOAMANAGER ( though we haven't tried to load into Flex).

We get errors becasue the application does not like the <wsp:Policy> elements in the tag <wsdl:portType>. We have rasied an OSS message for this which is still in progress.

Cheers

Manish

[Former Member · Accepted solution]

Manish, thanks for the response. I got errors as well. In addition, If I look at my log in sm21, I get:

 SOAP Runtime ICX_SOAP_CORE: 1100 occurred in method AUTHORITY_CHECK of class CL_WS_SECURITY_PRO TOCOL at position 0                
 ICX_SOAP_CORE message: SRT: Authorization denied occurred in method AUTHORITY_CHECK of class CL_WS_SECURITY_PRO TOCOL at position 0

[Former Member]

Hi ,

I had a similar error "SRT: Authorization denied". where i could not enter input parameters.

It was fixed by assigning the role sap_qap_webservice

Regards

Ram

[Former Member]

Can someone post the resolution to this problem?

We also have the issue of compiling MW web service clients using the new WSDL; it appears to require a <wsp:UsingPolicy> attribute, where none was required/produced before we upgraded to NetWeaver 7.1. Since the web services are secured via web server Basic Authentication, no policy should be needed, right?

[Former Member]

in your WSDL URL replace ws_policy by standard and it will work (without WS Policy).

AFAIK, no advanced WS-* functionality is provided by Flex out of the box.

anton

[former_member339862]

Hi,

I am also facing the same error. Can anyone tell me, how this problem can be solved?.

Thanks & regards,

Harsha

Hindustan unilever ltd.

[Former Member]

Hi Yves:

Do you have any j2ee server or j2ee add-in integrated on the server, it might be the WSDL version is not compatible with the Flex version you are using. It sometimes could happen. SAP is capable to generate WSDL with other configurations. Try enter on the WSADMIN and see if you could find the service. There is button where to get the WSDL, it can be generated with two possible version.

Kind regards

Gonzalo Perez-Prim

[Former Member]

the same problem generating Axis2 clients. There is no module extension for:

cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/commit/type assertions

cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/transaction/type assertions

cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/wsrm/type assertions

cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/blocking/type assertions

hmm...

Best regards

T. Kis