I hope this helps you . Since you are migrating to Jboss from WebSphere and you are using "com.ibm.websphere.naming.WasInitialContextFactory" class, which is WAS specific class, that's why you are getting this error. Change that to "org.jboss.naming.remote.client.InitialContextFactory" and then try again. That should resolve your issue. UPDATE
Does that help The WebSphere Application Server Community Edition isn't a real WebSphere application server. Its a "pimped" Apache Geronimo. I wouldn't count on seeing any IBM classes in the Community Edition that where present in your AIX WebSphere.
Jar file for com.ibm.websphere.naming.WsnInitialContextFactory
By : Archana N
Date : March 29 2020, 07:55 AM
fixed the issue. Will look into that further You certainly need the WAS_ROOT/runtimes/com.ibm.ws.ejb.thinclient_8.0.0.jar in your classpath, where WAS_ROOT is the installation home of your WAS.
hop of those help? You should use another connecting attributes while preparing InitialContext. There is no jnp in jboss 7.1.1, so you should set property "java.naming.factory.initial" to value "org.jboss.naming.remote.client.InitialContextFactory". Also property PROVIDER_URL should be "remote://localhost:4447" (not "localhost:1099") and you should also specify the username and credential (password) in the properties map given to the InitialContext as parameter.
may help you . I spent a day following tutorials and ebooks (and forum solutions too) for JBoss 6. The main "problem" is JBoss 7 has a different approach for JNDI settings and with InitialContext. Finally I found a tutorial that saved my day, hope this can help you too: