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 coderanch.com by Unknown author, 1 year ago
via coderanch.com by Unknown author, 1 year ago
com.sun.webui.jsf.faces.UIComponentELResolver: 	at org.glassfish.web.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1985)	at org.glassfish.web.loader.WebappClassLoader.findClass(WebappClassLoader.java:888)	at org.glassfish.web.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1420)	at com.sun.faces.util.Util.loadClass(Util.java:203)	at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:313)	at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:240)	at com.sun.faces.config.processor.ApplicationConfigProcessor.addELResolver(ApplicationConfigProcessor.java:560)	at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:298)	at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)	at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116)	at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114)	at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:223)	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:335)