You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/09/11 07:07:32 UTC
[jira] Created: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
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
Fix For: 1.1.0
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
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Attachment: TRANSPORTS-16.patch
Attaching the fix
> 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
> 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
[jira] Commented: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912382#action_12912382 ]
Hiranya Jayathilaka commented on TRANSPORTS-16:
-----------------------------------------------
This may be the cause of https://issues.apache.org/jira/browse/SYNAPSE-436
> 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
> 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
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Attachment: TRANSPORTS-16.patch
Attaching the fix
> 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
> 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
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Attachment: TRANSPORTS-16.patch
Attaching the fix
> 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
> 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
[jira] Commented: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912382#action_12912382 ]
Hiranya Jayathilaka commented on TRANSPORTS-16:
-----------------------------------------------
This may be the cause of https://issues.apache.org/jira/browse/SYNAPSE-436
> 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
> 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
[jira] Commented: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912382#action_12912382 ]
Hiranya Jayathilaka commented on TRANSPORTS-16:
-----------------------------------------------
This may be the cause of https://issues.apache.org/jira/browse/SYNAPSE-436
> 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
> 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
[jira] Commented: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912382#action_12912382 ]
Hiranya Jayathilaka commented on TRANSPORTS-16:
-----------------------------------------------
This may be the cause of https://issues.apache.org/jira/browse/SYNAPSE-436
> 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
> 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
[jira] Commented: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912382#action_12912382 ]
Hiranya Jayathilaka commented on TRANSPORTS-16:
-----------------------------------------------
This may be the cause of https://issues.apache.org/jira/browse/SYNAPSE-436
> 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
> 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
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Attachment: TRANSPORTS-16.patch
Attaching the fix
> 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
> 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
[jira] Updated: (TRANSPORTS-16) JMS Transport Cannot be Used to
Receive Messages from JMS Topics
Posted by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TRANSPORTS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated TRANSPORTS-16:
------------------------------------------
Attachment: TRANSPORTS-16.patch
Attaching the fix
> 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
> 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