You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/09/16 19:04:44 UTC

[jira] Created: (OPENEJB-917) JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()

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


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.


[jira] Closed: (OPENEJB-917) JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (OPENEJB-917) JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OPENEJB-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631477#action_12631477 ] 

Jarek Gawor commented on OPENEJB-917:
-------------------------------------

Btw, the is org.apache.openejb.core.singleton.EjbWsContext and org.apache.openejb.core.stateless.EjbWsContext which are identical at this point. If they are going to be the same in the future, it might be nicer to have one copy of this class and move it to org.apache.openejb.core.webservices package (or something like that).


> 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.


[jira] Updated: (OPENEJB-917) JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Assigned: (OPENEJB-917) JAX-WS 2.1: Support for WebServiceContext.getEndpointReference()

Posted by "David Blevins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins reassigned OPENEJB-917:
-------------------------------------

    Assignee: Jarek Gawor

> 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
>            Assignee: 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.