WildFly Naming Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 18: | Line 18: | ||
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: {{Internal|WildFly_JNDI_Concepts#Exporting_for_access_by_Remote_JNDI_Clients|WildFly JNDI Concepts - Exporting for Access by Remote JNDI Clients}} | 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: {{Internal|WildFly_JNDI_Concepts#Exporting_for_access_by_Remote_JNDI_Clients|WildFly JNDI Concepts - Exporting for Access by Remote JNDI Clients}} | ||
==Importing an External JNDI Context== | |||
Revision as of 17:48, 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: