@Eager不可用。 EagerBeansRepository无法从CDI bean管理器获取 [英] @Eager is unavailable. The EagerBeansRepository could not be obtained from CDI bean manager
问题描述
这是我第一次使用omnifaces。
我的应用运行良好，但没有它，但是当我尝试它时，我得到以下异常。
java.lang.NullPointerException在org.omnifaces.cdi.eager.EagerBeansPhaseListener.afterPhase（EagerBeansPhaseListener.java:50）
在com.sun.faces.lifecycle.Phase.handleAfterPhase（Phase.java:189）
at com.sun.faces.lifecycle.Phase.doPhase（Phase.java:107）
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase（RestoreViewPhase.java:123）
at com.sun .faces.lifecycle.LifecycleImpl.execute（LifecycleImpl.java:198）
位于javax.faces.webapp.FacesServlet.service（FacesServlet.java:658）
位于org.apache.catalina.core.StandardWrapper .Service（StandardWrapper.java:1550）
at org.apache.catalina.core.StandardWrapperValve.invoke（StandardWrapperValve.java:281）
at org.apache.catalina.core.StandardContextValve.invoke（StandardContextValve .java：175）
在org.apache.catalina.core.StandardPipeline.doInvoke（StandardPipeline.java:65 5）
at org.apache.catalina.core.StandardPipeline.invoke（StandardPipeline.java:595）
at org.apache.catalina.core.StandardHostValve.invoke（StandardHostValve.java:161）$ b在org.apache.catalina.connector.CoyoteAdapter.doService（CoyoteAdapter.java:331）
$ b在org.apache.catalina.connector.CoyoteAdapter.service（CoyoteAdapter.java:231）
。在COM .sun.enterprise.v3.services.impl.ContainerMapper $ AdapterCallable.call（ContainerMapper.java:317）
at com.sun.enterprise.v3.services.impl.ContainerMapper.service（ContainerMapper.java:195）在com.sun.grizzly.http.ProcessorTask.invokeAdapter（ProcessorTask.java:860）
在com.sun.grizzly.arp.DefaultAsyncExecutor.execute（DefaultAsyncExecutor.java:159）
在com.sun.grizzly.arp.DefaultAsyncExecutor.interrupt（DefaultAsyncExecutor.java:145）
在com.sun.grizzly.arp.AsyncProcessorTask.doTask（AsyncProcessorTask.java:102）
在的com.sun .grizzly.http.TaskBase.run（TaskBase.java:193）
at com.sun.grizzly.http.TaskBase.execute（TaskBase.java:175）
at com.sun.grizzly.arp.DefaultAsyncHandler.handle（DefaultAsyncHandler.java:145）
at com.sun .grizzly.arp.AsyncProtocolFilter.execute（AsyncProtocolFilter.java:210）
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter（DefaultProtocolChain.java:137）
at com.sun.grizzly.DefaultProtocolChain.execute （DefaultProtocolChain.java:104）
at com.sun.grizzly.DefaultProtocolChain.execute（DefaultProtocolChain.java:90）
at com.sun.grizzly.http.HttpProtocolChain.execute（HttpProtocolChain.java:79 ）维持在com.sun.grizzly.SelectionKeyContextTask.call（SelectionKeyContextTask.java:59）
com.sun.grizzly.ProtocolChainContextTask.doCall（ProtocolChainContextTask.java:54）
。在COM
。 sun.grizzly.ContextTask.run（ContextTask.java:71）
at com.sun.grizzly.util.AbstractThreadPool $ Worker.doWork（AbstractThreadPool.java:532）
at com.sun.grizzly。 util.AbstractThreadPool $禾rker.run（AbstractThreadPool.java:513）
at java.lang.Thread.run（Thread.java:745）
我在Netbeans中创建了一个新的空Web应用程序，使用以下代码在Glassfish 3.1.2.2
下运行：
OmniFaces 2.1版
Mojarra 2.2.12 PrimeFaces 5.3
PrimeFaces扩展3.2。
，但每次我在玻璃鱼启动过程中使用以下警告运行应用程序时，仍然会收到同样的错误：
$ b blockquote>
@Eager is不可用。 EagerBeansRepository无法从CDI bean管理器中获得。
请提供任何帮助吗？
当我从glassfish domain1 / lib目录中删除omnifaces-2.1.jar时，一切正常。
当我从glassfish domain1 / lib目录中删除omnifaces-2.1.jar时，一切正常。
Web库不属于那里。 Web库属于WAR的 / WEB-INF / lib 。当错误放置在 / WEB-INF / lib 之外时，webapp将无法在Web库中查找带有JSF / CDI注释的类并引发与此相关的异常。 / p>
将OmniFaces JAR文件从 domain1 / lib 放回到 / WEB-INF / lib 。然后，JSF将能够找到OmniFaces中捆绑的 @FacesComponent 注释类，而CDI将能够找到 @XxxScoped 类捆绑在OmniFaces中，例如 EagerBeansRepository 类。 OmniFaces主页：
安装
这是将OmniFaces 2.1 JAR文件放入
/ WEB-INF / lib中的一个问题。
...
OmniFaces被设计为WAR库（网页片段库），因此不能放在webapp的运行时类路径WAR之外的
/ WEB-INF / lib，例如EAR的/ lib甚至服务器或JRE自己的/ lib中。当OmniFaces JAR文件以这种方式错位时，那么webapp将无法在部署或运行时找到与OmniFaces绑定的JSF / CDI注释类并引发与此相关的异常。为了解决这个问题，把OmniFaces放在WAR的/ WEB-INF / lib中。
This is my first usage of omnifaces. My app works well without it but when I tried it I get the following exception.
java.lang.NullPointerException
at org.omnifaces.cdi.eager.EagerBeansPhaseListener.afterPhase(EagerBeansPhaseListener.java:50)
at com.sun.faces.lifecycle.Phase.handleAfterPhase(Phase.java:189)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:107)
at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:123)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:198)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:658)
at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1550)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:331)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:231)
at com.sun.enterprise.v3.services.impl.ContainerMapper$AdapterCallable.call(ContainerMapper.java:317)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
at com.sun.grizzly.arp.DefaultAsyncExecutor.execute(DefaultAsyncExecutor.java:159)
at com.sun.grizzly.arp.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:145)
at com.sun.grizzly.arp.AsyncProcessorTask.doTask(AsyncProcessorTask.java:102)
at com.sun.grizzly.http.TaskBase.run(TaskBase.java:193)
at com.sun.grizzly.http.TaskBase.execute(TaskBase.java:175)
at com.sun.grizzly.arp.DefaultAsyncHandler.handle(DefaultAsyncHandler.java:145)
at com.sun.grizzly.arp.AsyncProtocolFilter.execute(AsyncProtocolFilter.java:210)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
at java.lang.Thread.run(Thread.java:745)
I have created a new empty web app in Netbeans, run it under Glassfish 3.1.2.2 using : OmniFaces version 2.1 Mojarra 2.2.12 PrimeFaces 5.3 PrimeFaces Extensions 3.2. and still get the same error each time I run the app with the following warning during glass fish startup:
@Eager is unavailable. The EagerBeansRepository could not be obtained from CDI bean manager.
Any help please?
When I remove omnifaces-2.1.jar from glassfish domain1/lib directory, everything works fine.
When I remove omnifaces-2.1.jar from glassfish domain1/lib directory, everything works fine.
Web libraries doesn't belong there. Web libraries belong in /WEB-INF/lib of the WAR. When misplaced outside /WEB-INF/lib, then the webapp won't be able to find JSF/CDI annotated classes in the web library and throw exceptions related to this.
Put back OmniFaces JAR file from domain1/lib into /WEB-INF/lib. Then JSF will be able to find @FacesComponent annotated classes bundled in OmniFaces and CDI will be able to find @XxxScoped classes bundled in OmniFaces, such as the EagerBeansRepository class.
See also "Installation" section of OmniFaces homepage:
Installation
It is a matter of dropping the OmniFaces 2.1 JAR file in
/WEB-INF/lib....
OmniFaces is designed as a WAR library (web fragment library) and therefore can't be placed elsewhere in the webapp's runtime classpath outside WAR's own
/WEB-INF/lib, such as EAR's/libor even server's or JRE's own/lib. When OmniFaces JAR file is misplaced this way, then the webapp will be unable to find OmniFaces-bundled JSF/CDI annotated classes and throw exceptions related to this during deploy or runtime. To solve it, put back OmniFaces in WAR's/WEB-INF/lib.
这篇关于@Eager不可用。 EagerBeansRepository无法从CDI bean管理器获取的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
