WildFly JNDI Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
{{Internal|WildFly Remote Programmatic JNDI Access|Remote Programmatic JNDI Access}} | {{Internal|WildFly Remote Programmatic JNDI Access|Remote Programmatic JNDI Access}} | ||
=HA JNDI= | |||
<font color=red>TODO | |||
* https://access.redhat.com/solutions/436843 | |||
* https://access.redhat.com/solutions/1155493 | |||
What does this mean? remoting://host1:4447,host2:4547 | |||
</font> | |||
Revision as of 05:38, 18 March 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".
Remote Programmatic JNDI Access
HA JNDI
TODO
What does this mean? remoting://host1:4447,host2:4547