WildFly JNDI Concepts: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * WildFly JNDI") |
No edit summary |
||
| Line 2: | Line 2: | ||
* [[WildFly JNDI]] | * [[WildFly JNDI]] | ||
=Exporting for access by Remote JNDI Clients= | |||
If an object registered to JNDI is supposed to be looked up by remote (running in different JVM) JNDI clients, then the object must be registered under the "java:jboss/exported" JNDI context. When it is looked up remotely, the "java:jboss/exported" prefix must be omitted. | |||
For example, a JMS queue registered under "java:jboss/exported/jms/queue/TestQueue" can be looked up remotely as "jms/queue/TestQueue". | |||
Revision as of 22:06, 6 February 2017
Internal
Exporting for access by Remote JNDI Clients
If an object registered to JNDI is supposed to be looked up by remote (running in different JVM) JNDI clients, then the object must be registered under the "java:jboss/exported" JNDI context. When it is looked up remotely, the "java:jboss/exported" prefix must be omitted.
For example, a JMS queue registered under "java:jboss/exported/jms/queue/TestQueue" can be looked up remotely as "jms/queue/TestQueue".