[jbosstools-issues] [JBoss JIRA] (JBIDE-20562) WildFly: jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime list

Fri Sep 11 09:46:01 EDT 2015

    [ https://issues.jboss.org/browse/JBIDE-20562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107883#comment-13107883 ] 

carl zhang commented on JBIDE-20562:
------------------------------------

1. You are right. jsf-impl jar can be removed if the project does not use its classes. I comment all classes which are from jsf-impl. project can compile and run (the related function lost)

2. 
>Users can already customize the list of what jars are added to their project's classpath
Do you mean fix? 
Mine is WildFly 8.2.0-Final. Here is the error message when adding jsf-impl-2.2.8.jar to project classpath (I replace jsf-api and jsf-impl jars with the 2.2.8 version)

09:21:12,290 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-19) Initializing Mojarra 2.2.8 ( 20140814-1418 https://svn.java.net/svn/mojarra~svn/tags/2.2.8@13507) for context '/e-services'09:21:14,708 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-19) 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) [jsf-impl-2.2.8.jar:2.2.8] at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:378) [jsf-impl-2.2.8.jar:2.2.8] at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:321) [jsf-impl-2.2.8.jar:2.2.8] at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:270) [jsf-impl-2.2.8.jar:2.2.8] at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:437) [jsf-impl-2.2.8.jar:2.2.8] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8.jar:2.2.8] at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final] at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]09:21:14,708 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-19) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./e-services: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./e-services: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_40] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_40] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_40]Caused by: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:222) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] ... 3 moreCaused by: java.lang.RuntimeException: 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.ConfigureListener.contextInitialized(ConfigureListener.java:280) at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) ... 7 moreCaused by: 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:437) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) ... 9 more09:21:14,708 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./e-services" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./e-services: Failed to start service    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined    Caused by: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined    Caused by: com.sun.faces.config.ConfigurationException: The tag named inputFile from namespace http://xmlns.jcp.org/jsf/html has a null handler-class defined"}}09:21:14,850 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "e-services.war" with deployment "e-services.war"09:21:14,850 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

If remove it from project classpath, then add the same jar to WildFly 8.2.0-Final Default classpath. There is no error message when build, deploy and run.

> WildFly: jsf-impl-2.2.8-jbossorg-1.jar is not in default Runtime list
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-20562
>                 URL: https://issues.jboss.org/browse/JBIDE-20562
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.3.0.CR1
>            Reporter: carl zhang
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 4.3.x
>
>
> In Eclipse, I chose WildFly 8.2.0 server as my local web server. Then I created Dynamic Web Project. After done, I check the project Libraries-->WildFly 8.x Runtime libraries. I can see jboss-jsf-api_2.2_spec-2.2.8.jar in the list, but cannot see jsf-impl-2.2.8-jbossorg-1.jar
> So my Java codes related to jsf-impl classes cannot pass the compile. And I cannot manually add jsf-impl.jar into the project WEB_INF/lib because it cause deployment conflict.
> Please add the jsf-impl jar file into default Runtime library list. I don't check 9.0.0 and 10.0.0, if it is not in their default list. Please add it in

--
This message was sent by Atlassian JIRA
(v6.4.11#64026)