[
http://jira.jboss.com/jira/browse/JBMESSAGING-1183?page=all ]
Jeff Mesnil resolved JBMESSAGING-1183.
--------------------------------------
Resolution: Done
- committed in Branch_Stable (r3768) for version 1.4.1.beta2
- merged in JBossMessaging_1_4_0_SP3_CP (r3770) from r3768 for version 1.4.0.SP3.CP02
( also committed in trunk for JBM 2.0 (r3771) but kept the code commented)
Message Bridge use QueueFactoryRef or TopicFactoryRef instead of
FactoryRef when looking up Source and Target Connection Factories
----------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1183
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1183
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.0.SP1
Reporter: Aaron Walker
Assigned To: Jeff Mesnil
Priority: Minor
Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2
Some message providers don't have a single base class the implements both the Queue
and Topic Connection Factories so you can't create a single JMSProviderLoader where
you can set the FactoryRef attribute to a single JNDI name. Really the Message bridge
should use the QueueFactoryRef or TopicFactoryRef attribute depending on the destination
type that the bridge is trying to connect to.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira