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 "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/12/01 08:10:10 UTC
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Priority: Critical (was: Major)
This is actually a very critical issue. Because of this the JMS transport cannot be used to connect to JMS topics at all. Can I get some feedback on the patch?
> JMS Transport Cannot be Used to Receive Messages from JMS Topics
> ----------------------------------------------------------------
>
> Key: TRANSPORTS-16
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-16
> Project: Axis2 Transports
> Issue Type: Bug
> Components: JMS
> Affects Versions: 1.0.0
> Environment: Any
> Reporter: Hiranya Jayathilaka
> Priority: Critical
> Fix For: 1.1.0
>
> Attachments: TRANSPORTS-16.patch
>
>
> 1. Setting the transport.jms.DestinationType parameter to "topic" does not work. The value is always overwritten by the default value of "queue".
> 2. The above issue can be worked around by setting the transport.jms.ReplyDestinationType parameter (to any value). But still when looking up the JMS destinations, the transport will lookup a queue destination and not a topic destination.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org