WildFly Remote Programmatic JNDI Access: Difference between revisions
Jump to navigation
Jump to search
(→Code) |
|||
| Line 13: | Line 13: | ||
=Classpath= | =Classpath= | ||
The client's classpath must include $JBOSS_HOME/bin/client/jboss-client.jar. | The client's classpath must include <tt>$JBOSS_HOME/bin/client/jboss-client.jar</tt>. | ||
=API= | =API= | ||
Revision as of 18:21, 7 February 2017
Internal
Relevance
EAP 7
Overview
This article describes remote programmatic JNDI access for WildFly/EAP. The article was written using an EAP 7.0.4 instance.
Classpath
The client's classpath must include $JBOSS_HOME/bin/client/jboss-client.jar.
API
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "http-remoting://<hostname>:8080");
context = new InitialContext(properties);
Queue myTestQueue = (Queue) context.lookup("jms/queue/myTestQueue");