Soap sender does give some connectivity errors or HTTP error codes to the sender system to someextent during connectivity or mapping errro. The sender system should catch those errors in their web service client class for their requirement. But if you expect the whole meaningful error trace then it won't does that. Example If the soap adapter is not up and running and if you post a message to the soap sender adapter you might get the adapter service is not available. You might get http 500 error for the mapping. Even if you do convert the scenario to synchronous the same behavior. If you use ccbpm then using send and receive steps you can capture system acknowledgements.
↧