Hi,
my scenario is 3rd party (SOAP) to NetWeaver BPM (synchronous).
The message sender requires to check the message content for a couple of values and - in case of missmatch - sending back a SOAP fault message with http status 400. The sender provides a wsdl having a soap fault message, which i used in the interfaces as fault message.
I tried to setup an escalation/error end in the BPM, where i can choose the correspoding fault type. Looks very promising. But in runtime the process just breaks down, there is no answer at all. If you look to the NWDS help under "Events" you ll find:
"You use error end events to model an error that
occurs in the process. This error triggers a WSDL fault which can be defined in
the service interface of the message trigger you assign to a message start
event. As the error is defined in the service interface, it is visible outside
the BPM system and can be used for communication with other systems.
There can be as many error end events in a process
as the number of faults defined, but you cannot model a synchronous process
ending with an error end event because WSDL fault response is not supported."
So does anybody here have a solution or at least an idea how to solve the problem?
If i map a "real" response to the fault type (in the operation mapping) i think it will not be executed.
If i use "do not use soap envelope" in the adapter, map all the soap envelope for myself and create in case i need it the soap fault for example with xslt, then i don't think i would get http status 400 - instead 200 for success.
/Udo