Similar problem, however, I'm using portlets, running things inside the same
JVM and everything runs inside the same app, however, in some places my app uses
TransactionManager tm = (TransactionManager)new
InitialContext().lookup("java:/TransactionManager") ;
... wich runs nice and smooth, while some other places, INSIDE THE VERY SAME
APPLICATION, with the very same identical code, print this error:
javax.naming.NoInitialContextException: Cannot instantiate class:
org.jnp.interfaces.NamingContextFactory [Root exception is
java.lang.ClassNotFoundException: org/jnp/interfaces/NamingContextFactory]
| at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
| at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
| at javax.naming.InitialContext.init(InitialContext.java:223)
| at javax.naming.InitialContext.<init>(InitialContext.java:175)
| at portlets.performers.ActionPerformer.flushPersistence(Unknown
Source)
| at portlets.performers.ActionPerformer.finalize(Unknown Source)
| at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
| at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
| at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
| at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
| Caused by: java.lang.ClassNotFoundException:
org/jnp/interfaces/NamingContextFactory
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:247)
| at
com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
| at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
| ... 9 more
... weird, huh ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994359#3994359
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994359
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
