JNDI can be checked on the naming subsystem of the application server. You can check the JNDI binding in two ways: from the CLI or from the Web admin interface

Using CLI

[disconnected /] connect
[standalone@localhost:9999 /] /subsystem=naming:jndi-view
{
    "outcome" => "success",
    "result" => {
        "java: contexts" => {
            "java:" => {
                "ConnectionFactory" => {
                    "class-name" => "org.hornetq.jms.client.HornetQJMSConnection
Factory",
                    "value" => "HornetQConnectionFactory [serverLocator=ServerLo
catorImpl [initialConnectors=[org-hornetq-core-remoting-impl-invm-InVMConnectorF
actory?server-id=0], discoveryGroupConfiguration=null], clientID=null, dupsOKBat
chSize=1048576, transactionBatchSize=1048576, readOnly=false]"
                },
. . . . .
}

Using the Web Admin Console

Just log in to the admin console and have a look at the Container | Naming tab.
Here's a shortcut for it: http://localhost:9990/console/App.html#naming

jndi-view jboss as 7 jndi

0
0
0
s2smodern

Related articles available on mastertheboss.com

JBoss AS 7 introduction

This is an introduction tutorial to the newest JBoss AS 7 which a

Develop Java EE applications on WildFly

In this tutorial we will learn how to develop a basic Java EE 8 a

Adding users with JBoss AS 7

If you are planning to add new users to your management interface

Using JBoss AS 7 management API programmatically

In this tutorial we will show how to use detyped management API t

How to install a module on WildFly / JBoss AS 7

Installing a module on WildFly / JBoss AS 7 requires creating a p

WildFly / JBoss EAP classloading explained

JBoss EAP / WildFly classloading explained As mandated by Java E

W

i

l

d

F

l

y

 

c

h

e

a

t

s

h

e

e

t