[
http://jira.jboss.com/jira/browse/JBMESSAGING-1183?page=comments#action_1... ]
Aaron Walker commented on JBMESSAGING-1183:
-------------------------------------------
It's JMS 1.1 but it's Websphere MQ ;)
The WSMQ destinations and connection factories get bound into JNDI using a custom MBean
that use the IBM API to create them
But if you use the WSMQ JCA adpater you end with the same result. Separate Queue and Topic
connection factories.
Also if you want to maintain backward compatibility the you should use the FactoyRef if
it's set otherwise check the destination type.
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: Aaron Walker
Priority: Minor
Fix For: Stable branch
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