[
https://issues.apache.org/jira/browse/OPENEJB-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor updated OPENEJB-917:
--------------------------------
Attachment: OPENEJB-917.patch
The attached patch adds an AddressingSupport interface that defines
getEndpointReference() functions and modifies the EjbWsContext class to
delegate the getEndpointReference() calls to the AddressingSupport functions.
Each JAX-WS provider will have its own implementation of the AddressingSupport
interface and will pass an instance of it on the Web Service invocation (like
the MessageContext or Interceptor today).
In cases where the AddressingSupport instance is not passed with the request,
the default NoAddressingSupport will be used which will generate the
UnsupportedOperationException (just like before).
> JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()
> ----------------------------------------------------------------
>
> Key: OPENEJB-917
> URL: https://issues.apache.org/jira/browse/OPENEJB-917
> Project: OpenEJB
> Issue Type: New Feature
> Components: webservices
> Affects Versions: (trunk/openejb3)
> Reporter: Jarek Gawor
> Attachments: OPENEJB-917.patch
>
>
> In order to support JAX-WS 2.1, the EjbWsContext.getEndpointReference()
> methods need to be implemented correctly. Each JAX-WS provider (Axis2, CXF,
> etc.) has its own way of creating the EndpointReference and so
> EjbWsContext.getEndpointReference() will need to delegate the call to some
> provider-specific function to generate the EndpointReference.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
