[
https://issues.jboss.org/browse/WFLY-327?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on WFLY-327:
----------------------------------------------
mark yarborough <myarboro(a)redhat.com> changed the Status of [bug
912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] from VERIFIED to CLOSED
Remote JNDI is not working with a HornetQ-only JMS bridge
---------------------------------------------------------
Key: WFLY-327
URL:
https://issues.jboss.org/browse/WFLY-327
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: JMS
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: 8.0.0.Alpha1
The jms-bridge can be used to bridge a hornetq server to another and should work by
specifying to use the org.hornetq.module to load the JMS implementation classes.
However, this fails because this module does not have access to the JBoss remote-naming
module that is required to connect to remote JBoss JNDI server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira