[
https://issues.apache.org/jira/browse/OPENEJB-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins closed OPENEJB-917.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.1
Sending
container/openejb-core/src/main/java/org/apache/openejb/core/singleton/EjbWsContext.java
Sending
container/openejb-core/src/main/java/org/apache/openejb/core/singleton/SingletonContainer.java
Sending
container/openejb-core/src/main/java/org/apache/openejb/core/stateless/EjbWsContext.java
Sending
container/openejb-core/src/main/java/org/apache/openejb/core/stateless/StatelessContainer.java
Adding
container/openejb-core/src/main/java/org/apache/openejb/core/webservices/AddressingSupport.java
Adding
container/openejb-core/src/main/java/org/apache/openejb/core/webservices/NoAddressingSupport.java
Transmitting file data ......
Committed revision 698737.
> 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
> Fix For: 3.0.1
>
> 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.
