A WSIT client is not informed explicitly when its WS-AtomicTransaction enabled
request is not working as expected. Specifically, when a wscoor:register fails
due to such reasons as (1) firewall blocking request (2) misconfigured security
certificates on client or transacted web service side (3) .....
Currently, the following SEVERE message is printed in server log of
transacted web service when a wscoor:register fails.
SEVERE WSTX-AT-0022: Registration with durable parent failed:
This it is not obvious on client side when a distributed WS-Atomic Transaction
that should be in effect is not working properly w/o analyzing sevver log.
Recommended remedy is to also throw a WebServiceException. The Exception
message would contain text as SEVERE message and the exception that
caused the register to fail would be nested within the WebServiceException.
The client benefits from the more immediate feedback that WS-AT 2 phase commit
is not possible due to some network configuration issue.