[WSCOMMONS-468] The JMS transport doesn't use the ActiveMQ hack consistently

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Transports 1.0
• Component/s: Transport
• Assignee: Ruwan Linton
• Reporter: Andreas Veithen
• Created: 10/May/09 18:06
• Updated: 13/Oct/09 14:48
• Resolved: 13/Oct/09 14:48

Description

JMSOutTransportInfo#getDestination contains an ActiveMQ specific hack that prefixes the destination JNDI name with "dynamicQueues/" or "dynamicTopics/" if the initial lookup fails. On the other hand, JMSConnectionFactory#getDestination doesn't apply this hack. This means that the behavior in the JMSSender is inconsistent and depends on whether an existing connection factory definition is found in axis2.xml or not.

In addition, ServiceTaskManager#getDestination uses yet another approach, namely to get the Destination object from Session#createQueue or Session#createTopic.

Note that I believe that adding provider specific hacks is bad and I'm -1 for a solution that would simply add the hack to JMSConnectionFactory#getDestination.