WildFly Remote Programmatic JNDI Access

Internal

• WildFly JNDI Concepts

Relevance

• EAP 6
• EAP 7

Overview

This article describes remote programmatic JNDI access for WildFly/EAP. The article was written using an EAP 7.0.4 instance.

EAP 7

EAP7 Remote Programmatic JNDI Access Classpath

The client's classpath must include $JBOSS_HOME/bin/client/jboss-client.jar.

EAP7 Remote Programmatic JNDI Access API

Properties properties = new Properties();

properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "http-remoting://localhost:8080");

Context c = new InitialContext(properties);

Queue myTestQueue = (Queue)c.lookup("jms/queue/myTestQueue");

EAP7 Remoting

The remoting subsystem URL to access the JNDI service is "http-remoting://<host>:8080". For more details, see:

The Remoting Subsystem

EAP7 Code

https://github.com/NovaOrdis/playground/tree/master/jboss/jndi/simplest-eap7

EAP 6

EAP6 Remote Programmatic JNDI Access Classpath

The client's classpath must include $JBOSS_HOME/bin/client/jboss-client.jar.

EAP6 Remote Programmatic JNDI Access API

Properties properties = new Properties();

properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "remote://localhost:4447");

Context c = new InitialContext(properties);

Queue myTestQueue = (Queue)c.lookup("jms/queue/myTestQueue");

EAP6 Remoting

The remoting subsystem URL to access the JNDI service is "remote://<host>:4447". For more details, see:

The Remoting Subsystem

EAP6 Code

https://github.com/NovaOrdis/playground/tree/master/jboss/jndi/simplest-eap6