You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Brian DePradine (JIRA)" <ji...@apache.org> on 2006/07/11 16:36:29 UTC

[jira] Created: (AXIS2-886) New JMS sender should take account of WS-Addressing destination even on the server

New JMS sender should take account of WS-Addressing destination even on the server
----------------------------------------------------------------------------------

         Key: AXIS2-886
         URL: http://issues.apache.org/jira/browse/AXIS2-886
     Project: Apache Axis 2.0 (Axis2)
        Type: Bug

  Components: transports  
    Reporter: Brian DePradine


The new JMS implementation of JMSSender does not take account of the WS-Addressing destination on the server. Patch to follow.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-886) New JMS sender should take account of WS-Addressing destination even on the server

Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-886?page=all ]

Brian DePradine updated AXIS2-886:
----------------------------------

    Attachment: patch.txt

Added my patch.

> New JMS sender should take account of WS-Addressing destination even on the server
> ----------------------------------------------------------------------------------
>
>          Key: AXIS2-886
>          URL: http://issues.apache.org/jira/browse/AXIS2-886
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: transports
>     Reporter: Brian DePradine
>  Attachments: patch.txt
>
> The new JMS implementation of JMSSender does not take account of the WS-Addressing destination on the server. Patch to follow.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Resolved: (AXIS2-886) New JMS sender should take account of WS-Addressing destination even on the server

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-886?page=all ]
     
Davanum Srinivas resolved AXIS2-886:
------------------------------------

    Resolution: Fixed

Applied.

thanks,
dims

> New JMS sender should take account of WS-Addressing destination even on the server
> ----------------------------------------------------------------------------------
>
>          Key: AXIS2-886
>          URL: http://issues.apache.org/jira/browse/AXIS2-886
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug

>   Components: transports
>     Reporter: Brian DePradine
>  Attachments: patch.txt
>
> The new JMS implementation of JMSSender does not take account of the WS-Addressing destination on the server. Patch to follow.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org