This issue is to do with the use of FactoryRef attribute from the JMSProviderLoader when looking up the ConnectionFactory in JNDI. It's actually valid not to provide one when create a JMSProviderLoader. Certain unnamed message providers don't have a single based class that implements both the Queue and Topic connection factories. As a work around I created two different JMSProviderLoaders and and bound the Topic or Queue connection factory to the FactoryRef attribute. This is not ideal really the bridge should get the QueueFactoryRef or TopicFactoryRef depending on the destination type.
I can raise and JIRA for this and submit a patch if you want.... --Aaron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110811#4110811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110811 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
