WildFly Naming Subsystem Configuration: Difference between revisions
| Line 20: | Line 20: | ||
==Importing an External JNDI Context== | ==Importing an External JNDI Context== | ||
This section describes the configuration required to import an external JNDI context into the local JND namespace. The external JNDI context must be exported by a remote server. More details about external JNDI contexts are available here: {{Internal|WildFly_JNDI_Concepts#Declaring_an_External_JNDI_Context|External JNDI Contexts}}. | |||
Provided that remote JNDI objects have been bound into an externally exported context (java:/jboss/export) by a remote server, | |||
<pre> | <pre> | ||
| Line 29: | Line 34: | ||
"name" is the ''local'' JNDI name to bind to. | "name" is the ''local'' JNDI name to bind to. | ||
More details about external JNDI Contexts can be found here: | More details about external JNDI Contexts can be found here: | ||
A working example is available here: {{External|https://github.com/NovaOrdis/playground/tree/master/jboss/messaging/sending-and-receiving-from-remote-destinations}} | A working example is available here: {{External|https://github.com/NovaOrdis/playground/tree/master/jboss/messaging/sending-and-receiving-from-remote-destinations}} | ||
Revision as of 19:04, 3 April 2017
Internal
Overview
The "naming" subsystem contains configuration related to various JNDI namespaces.
<subsystem xmlns="urn:jboss:domain:naming:1.4">
<remote-naming/>
</subsystem>
Configuration
<remote-naming>
If present, this element activates the remote naming server, that allows access to items bound in the java:jboss/exported JNDI context. More details about the JBoss exported JNDI namespace and the remote naming server can be found here:
Importing an External JNDI Context
This section describes the configuration required to import an external JNDI context into the local JND namespace. The external JNDI context must be exported by a remote server. More details about external JNDI contexts are available here:
.
Provided that remote JNDI objects have been bound into an externally exported context (java:/jboss/export) by a remote server,
<property name="java.naming.security.principal" value="${remoting.user.name}"/>
<property name="java.naming.security.credentials" value="${remoting.password}"/>
"name" is the local JNDI name to bind to.
More details about external JNDI Contexts can be found here:
A working example is available here: