Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via sourceforge.net by Unknown author, 1 year ago
org.jnp.interfaces.NamingContextFactory]
via co.jp by Unknown author, 2 years ago
via Google Groups by Jarek, 5 months ago
org.jnp.interfaces.NamingContextFactory]
via jboss.org by Unknown author, 1 year ago
via Oracle Community by 843833, 1 year ago
org.jnp.interfaces.NamingContextFactory]
via Google Groups by TrICkY, 4 months ago
org.jnp.interfaces.NamingContextFactory]
java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)	at javax.naming.InitialContext.init(InitialContext.java:219)	at javax.naming.InitialContext.(InitialContext.java:175)	at org.jboss.web.AbstractWebContainer.parseWebAppDescriptors(AbstractWebContainer.java:593)	at org.jboss.web.AbstractWebContainer$DescriptorParser.parseWebAppDescriptors(AbstractWebContainer.java:1116)	at org.jboss.jetty.JBossWebApplicationContext.setUpENC(JBossWebApplicationContext.java:313)	at org.jboss.jetty.JBossWebApplicationContext.startHandlers(JBossWebApplicationContext.java:275)	at org.mortbay.http.HttpContext.start(HttpContext.java:1740)	at org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:471)	at org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationContext.java:85)	at org.jboss.jetty.Jetty.deploy(Jetty.java:409)	at org.jboss.jetty.JettyService.performDeploy(JettyService.java:243)