WildFly Remote Programmatic JNDI Access: Difference between revisions
Jump to navigation
Jump to search
(→API) |
(→API) |
||
Line 29: | Line 29: | ||
</pre> | </pre> | ||
=Remoting= | |||
The remoting subsystem URL to access the JNDI service is "http-remoting://<host>:8080". For more details, see: | |||
{{Internal}} | |||
=Code= | =Code= | ||
{{External|https://github.com/NovaOrdis/playground/tree/master/jboss/jndi/simplest-eap7}} | {{External|https://github.com/NovaOrdis/playground/tree/master/jboss/jndi/simplest-eap7}} |
Revision as of 20:34, 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://localhost:8080"); Context c = new InitialContext(properties); Queue myTestQueue = (Queue)c.lookup("jms/queue/myTestQueue");
Remoting
The remoting subsystem URL to access the JNDI service is "http-remoting://<host>:8080". For more details, see:
- [[{{{1}}}|{{{2}}}]]