[jira] Resolved: (AXIS2-2030) jms destination name error in j2ee container

["Asankha C. Perera (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AXIS2-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asankha C. Perera resolved AXIS2-2030.
--------------------------------------

    Resolution: Fixed

Fixed on trunk to be included for 1.2 release (Already included in first RC)

Thanks to John Turner for the patch

> jms destination name error in j2ee container
> --------------------------------------------
>
>                 Key: AXIS2-2030
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2030
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1
>         Environment: Axis2 1.1, Geronimo1.1.1, windows XP professional
>            Reporter: falom
>         Assigned To: Asankha C. Perera
>
> if axis2 jmslistner trys to listen to an available destination in a j2ee container, i.e. one queue in activemq in 
> geronimo, then axis2 jmslistner can connect to it only through java:comp/env/jms/testQueue, but axis2 also register the destination name as java:comp/env/jms/testQueue, not testQueue instead, so when a axis2  client send message to the queue, the axis2 engine can not find the service to call. JMSConnectionFactory can be enhanced to handle this problem. falom

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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