Miroslav Novak created AS7-3657: ----------------------------------- Summary: Change jndi context for connection factory and destination in configuration of messaging subsystem Key: AS7-3657 URL: https://issues.jboss.org/browse/AS7-3657 Project: Application Server 7 Issue Type: Feature Request Components: JMS Affects Versions: 7.1.0.CR1b Reporter: Miroslav Novak Assignee: Andy Taylor Fix For: 7.1.0.Final According to AS7-1338 remote jndi was implemented. All objects which should be reachable to remote jms clients (like destinations and connection factories) should be now registered under "java:jboss/exported/" context. I'm not sure which context we're going to use by default. It could be "java:jboss/exported/jms/" or simply "java:jboss/exported/" or some other context. Following peace of configuration I've already tried and works: {code} <jms-connection-factories> ... <!-- configuration for connection factory --> <connection-factory name="RemoteConnectionFactory"> <connectors> <connector-ref connector-name="netty"/> </connectors> <entries> <entry name="java:jboss/exported/jms/RemoteConnectionFactory" /> <!- this is the important part --> </entries> </connection-factory> ... </jms-connection-factories> <jms-destinations> ... <jms-queue name="testQueue"> <entry name="java:jboss/exported/jms/queue/test"/> <!- this is the important part --> </jms-queue> ... </jms-destinations> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira