Web Service Consumer Configuration via WSDL document

August 6, 2009 at 2:16 pm

[] [] [] [] [] [] [] [] [] [] [] [] [] [] []

Symptom
When configuring a Web Service (WS) consumer Logical Port (LP) in the single configuration view of transaction SOAMANAGER, you recognize, that any operation specific property value settings (especially the ’soapAction’ property) disapear when displaying this LP again after the creation has taken place.
On the very first time, these settings are actually just [...]

Accessing WSDL and endpoint URLs with ~

July 6, 2009 at 5:15 am

[] [] [] [] [] [] []

Symptom
- Invalid Response code (404) when accessing WSDL and Endpoint URLs containing special characters in MSIE07
- Web service binding data URL contains special characters encoded or decoded.
Other terms
encoded/decoded URL, WSDL, endpoint
Reason and Prerequisites
The web service can be registered with binding data URL encoded in application/x-www-form-urlencoded MIME format or as it is.
The fix ensures that when [...]

Corrections in conversion from RPC to Document style WSDLs

June 29, 2009 at 5:39 am

[] [] [] [] [] [] [] []

Symptom
Proxy generation from RPC-style WSDL fails. In particular this may happen with some CAF generated WSDLs.
Other terms
WSDL, RPC, CAF, proxy
Reason and Prerequisites
ABAP proxy does not support RPC style WSDL itself. Instead it uses the SIDL library in order to convert initial WSDL to SIDL format. In case RPC style WSDL is consumed, proxy [...]