-
1. Re: Remote JNDI entry binding in Naming Subsystem
ggam Dec 27, 2015 2:35 PM (in response to ggam)I've already found the solution.
A lookup can navigate through an external context. My working configuration is now:
<subsystem xmlns="urn:jboss:domain:naming:2.0">
<bindings>
<external-context name="java:/global/mqserver" module="org.jboss.as.naming" class="javax.naming.InitialContext" cache="true">
<environment>
<property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/>
<property name="java.naming.provider.url" value="http-remoting://localhost:8290"/>
<property name="java.naming.security.principal" value="remote"/>
<property name="java.naming.security.credentials" value="remote"/>
</environment>
</external-context>
<lookup name="java:global/ExportedTopic" lookup="java:/global/mqserver/jms/topic/prueba"/>
<lookup name="java:global/ExportedFactory" lookup="java:/global/mqserver/jms/RemoteConnectionFactory"/>
</bindings>
<remote-naming/>
</subsystem>
Obviously, the remote server needs to have the entries exported.