Spooky Exceptions (7) – The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined


Umgebung

  • Wildfly 10
  • EE7

Situation

Es kommt folgende ConfigurationException beim Start des Wildfly:

12:12:32,109 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 88) 
   Critical error during deployment: : com.sun.faces.config.ConfigurationException: 
   The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:422)
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:378)
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:321)
	at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:270)
	at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:441)
	at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227)
	at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200)
	at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171)
	at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
	at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
	at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)

Ursache

Es wurde eine JSF Implementierung (jar) mit der Anwendung deployed. Diese stört sich mit der durch WIldfly bereitgestellten. Bei der Verwendung von MyEclipse geschieht dies häufiger, da MyEclipse das JSF jar häufig in den deployment descriptor aufnimmt.

Ursache

Das Deployment des JSF jar verhindern

;-)

Du hast Fragen oder Anmerkungen? Kontakt: arndt@schoenb.de

,