[jboss-jira] [JBoss JIRA] (WFLY-1946) Severe error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"

[Stan Silvert (JIRA)]

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

Stan Silvert commented on WFLY-1946:
------------------------------------

That's always been a source of controversy.  IMO, JSF is a web tier technology that should only be available from the web tier.  It requires a servlet container and always assumes that it is running inside a servlet container context.  If you add it to the EAR then you are potentially pulling in references to things like HttpServletRequest and HttpSession.  When that occurs outside the web tier, lots of bad things happen.

Maybe Pete needs to be aware of this issue.  I don't see why extensions would not be scoped to a particular module.  I don't think we can just say that in the case of extensions we don't need to care about context and classloading.  That should be clearly defined.  

I'll ping Pete and see what he thinks about it.
                
> Severe error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"
> -------------------------------------------------------------------------------
>
>                 Key: WFLY-1946
>                 URL: https://issues.jboss.org/browse/WFLY-1946
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, JSF
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Frank Langelage
>            Assignee: Stan Silvert
>         Attachments: Jira-WFLY-1946.tar
>
>
> Deploy of test.ear shows a severe error:
> 00:23:21,917 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "test.ear" (runtime-name: "test.ear")
> 00:23:21,941 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "null" (runtime-name: "web.war")
> 00:23:21,942 INFO  [org.jboss.as.server.deployment#start] JBAS015876: Starting deployment of "null" (runtime-name: "ejb.jar")
> 00:23:22,080 INFO  [org.jboss.weld.deployer#deploy] JBAS016002: Processing weld deployment test.ear
> 00:23:22,121 INFO  [org.jboss.weld.deployer#deploy] JBAS016002: Processing weld deployment ejb.jar
> 00:23:22,141 INFO  [org.jboss.weld.deployer#deploy] JBAS016002: Processing weld deployment web.war
> 00:23:22,157 INFO  [org.jboss.weld.deployer#deploy] JBAS016005: Starting Services for CDI deployment: test.ear
> 00:23:22,192 INFO  [org.jboss.weld.deployer#start] JBAS016008: Starting weld service for deployment test.ear
> 00:23:22,734 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow#afterBeanDiscovery] Unable to obtain CDI 1.1 utilities for Mojarra
> 00:23:22,753 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view#afterBeanDiscovery] Unable to obtain CDI 1.1 utilities for Mojarra
> 00:23:23,099 INFO  [test.web.Startup#contextInitialized] contextInitialized
> 00:23:23,405 INFO  [org.wildfly.extension.undertow#registerDeployment] JBAS018210: Register web context: /intern/web
> 00:23:23,465 INFO  [org.jboss.as.server#handleResult] JBAS018559: Deployed "test.ear" (runtime-name : "test.ear")
> Although everything seems to be fine. App works without errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira