Round-trip debugging for consuming an external WSDL

[Former Member]

We're having problems with consuming WSDL's from the client's Web App (.NET). I've exhausted all the options for ABAP debugging of the core SOAP methods. I;m wondering is what tools ABAP might have for monitoring on-the-wire messages

The point I'm stuck is in the class CL_SOAP_HTTP_TPBND_ROOT, method HANDLE_STATUS_CODE on the following call:

• -1- get/analyse status code

call method m_response->get_status

importing code = httpcode

reason = httpreason.

I couldn't F5 into that method but the results of the call bring the error that's carried through and captured by CX_SOAP_FAULT in the class CL_SOAP_RUNTIME_CLIENT / method EXEC_PROCESSING with the reason "Object reference not set to an instance of an object".

So, as a recap how can I trace on-the-wire message to figure out whether and how the round-trip happened

[Former Member · Accepted solution]

If your web service provider .NET is not handling the exception scenarios using web service fault condition, how can you see what is happened at the other side of the bridge.

Check your WSDL and see whether each web service operation have FAult handling properly, also check with ur provider to whether he is returning the fault messages properly at a fault condition, if you do not have a message returned either as response or fault, how can u expect your client API can it?

Thanks

[Former Member]

Thank you, you've made an important assumption to have the fault condition handled in the WSDL. I'll ask .NET developers to modify the WSDL file and see what's going to be captured after it's modified

I'll update this thread when I've got something substantial