[jbossts-issues] [JBoss JIRA] (JBTM-1105) Setup client side interceptors based on WS-Policy in WSDL

[Tom Jenkinson (Jira)]

     [ https://issues.jboss.org/browse/JBTM-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-1105:
--------------------------------
    Priority: Optional  (was: Major)


> Setup client side interceptors based on WS-Policy in WSDL
> ---------------------------------------------------------
>
>                 Key: JBTM-1105
>                 URL: https://issues.jboss.org/browse/JBTM-1105
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>          Components: XTS
>            Reporter: Paul Robinson
>            Priority: Optional
>   Original Estimate: 3 days
>  Remaining Estimate: 3 days
>
> If the Service WSDL specifies a WS-Policy assertion, we know that WS-AT or WS-BA is required/supported and we should be able to setup this handler chain automatically. Another benefit is that we can catch, on the client side, the situation where no WS-AT or WS-BA transaction context is present. Currently we leave it up to the service to detect and as a result we have no control over how this fault will be propagated back to the client. For example, a WrongStateException could be thrown when the service tries to enlist a participant and a transaction is not present. The Client may receive a generic fault message back or, in this case some or all of the WrongStateException. In either case, the developer of the Client is unlikely to realise that this is due to there not being a transaction present when the service was invoked. If the service mandates a WS-AT or WS-BA transaction, but none is present, then the client handler throws a suitable exception explaining what went wrong. If the service supports (i.e. it is optional) a WS-AT or WS-BA transaction, then the interceptor ignores the situation where non exists.
> CXF seems to have a plugin point for adding WS-Policy assertion handlers. This could be the right integration point for this feature. This is to be investigated.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)