WildFly Naming Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
==Importing an External JNDI Context== | ==Importing an External JNDI Context== | ||
<pre> | |||
<property name="java.naming.security.principal" value="${remoting.user.name}"/> | |||
<property name="java.naming.security.credentials" value="${remoting.password}"/> | |||
</pre> | |||
"name" is the ''local'' JNDI name to bind to. | |||
More details about external JNDI Contexts can be found here: {{Internal|WildFly_JNDI_Concepts#Declaring_an_External_JNDI_Context|External JNDI Contexts}} | More details about external JNDI Contexts can be found here: {{Internal|WildFly_JNDI_Concepts#Declaring_an_External_JNDI_Context|External JNDI Contexts}} | ||
Revision as of 18: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
<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: