使用PrimePush时出现NullPointerException

Question

当我尝试初始化我的eventBus时,我得到一个NullPointerException:

位于sun.reflect.NativeMethodAccessorImpl.invoke0(本地方法)的sun.reflect.NativeMethodAccessorImpl.invoke(未知来源)的de.mrsfinster.web.livefeed.bean.FeedBean.init(FeedBean.java:179)中的java.lang.NullPointerException在org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation $ SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:77)的java.lang.reflect.Method.invoke(未知来源)的sun.reflect.DelegatingMethodAccessorImpl.invoke(未知来源) Org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:126)位于org.jboss.weld.interceptor的org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:102). proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:43)org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:28)at orm.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53)at de.mrsfinster.web位于org.jboss.weld的org.jboss.weld.interceptor.util.InterceptionUtils.executePostConstruct(InterceptionUtils.java:38)的.livefeed.bean.FeedBean $ Proxy $ _ $$ _ WeldSubclass.lifecycle_mixin _ $$ _ postConstruct(未知来源).在org.jboss.weld.bean.ManagedBean.create(ManagedBean)的org.jboss.weld.injection.producer.BeanInjectionTarget.postConstruct(BeanInjectionTarget.java:68)中的interceptor.util.InterceptionUtils.executePostConstruct(InterceptionUtils.java:50). java:153)at org.jboss.weld.util.bean.IsolatedForwardingBean.create(IsolatedForwardingBean.java:44)org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)atg.jboss.weld.context.PassivatingContextWrapper $ AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)at org.jboss.weld .manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)org.jboss.weld.el.AbstractWeldELResolver.lookup(AbstractWeldELResolver.java:107)org.jboss.weld.el.AbstractWeldELResolver.getValue(AbstractWeldELResolver.java:90 )在com.sun.faces.el.DemuxCompositeELResolver的javax.el.CompositeELResolver.getValue(CompositeELResolver.java:188)的org.jboss.as.jsf.injection.weld.ForwardingELResolver.getValue(ForwardingELResolver.java:46). _getValue(DemuxCompositeELResolver.java:176)位于com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:116)at com.sun.el.parser.AstValue.getBase(AstValue.java:151)at com.sun.el.parser.AstValue位于org.jboss的com.sun.el.MarsodExpressionImpl.invoke(MethodExpressionImpl.java:304)的com.sun.el.parser.AstValue.invoke(AstValue.java:275)中的.getTarget(AstValue.java:170).焊接.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)org.jboss.weld.util.el.ForwardingMethodExpression.invoke(在com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)的com中,org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)中的ForwardingMethodExpression.java:40) .faces.facelets.tag.jsf.core.位于javax.faces上的javax.faces.component.UIComponent $ ComponentSystemEventListenerAdapter.processEvent(UIComponent.java:2584)的javax.faces的javax.faces.event.SystemEvent.processListener(SystemEvent.java:108)中的DeclarativeSystemEventListener.processEvent(EventHandler.java:128)位于com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2190)的.event.ComponentSystemEvent.processListener(ComponentSystemEvent.java:118)位于com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2135) )在com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289)的com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247)org.jboss.as.jsf.injection.在com.sun上焊接.ForwardingApplication.publishEvent(ForwardingApplication.java:299).face.slife.RenderResponsePhase.execute(RenderResponsePhase.java:107)at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java: 219)位于io.undertow.servlet.handle上的io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)的javax.faces.webapp.FacesServlet.service(FacesServlet.java:647)上,位于io.undertow.servlet.handlers.security.ServletSecurityRoleHandler .handleRequest(ServletSecurityRoleHandler.java:61)位于org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)的io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)在io的io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43).在io.undertow.server.handler.PredicateHandler的io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56)上的undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131). handleRequest(PredicateHandler.java:43)at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45)at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:63)at io .undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58)位于io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)位于org.wildfly的io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) .extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)at io.undertow.server.handlers.PredicateHandler.handleRequest (PredicateHandler.java:43)io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261)位于io.undertow的io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:247). servlet.handlers.ServletInitialHandler.访问位于io.undertow的io.undertow.servlet.handler.ServletInitialHandler $ 1.handleRequest(ServletInitialHandler.java:166)的io.undertow.server.Connectors.executeRootHandler(Connectors.java:197)$ 000(ServletInitialHandler.java:76) .server.HttpServerExchange $ 1.run(HttpServerExchange.java:759)java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)at java.util.concurrent.ThreadPoolExecutor $ Worker.run(Unknown Source)at java.lang.Thread .run(未知来源)java.lang.Thread.run上的java.util.concurrent.ThreadPoolExecutor $ Worker.run(未知来源)的runWorker(未知来源)(未知来源)java.lang.Thread.run上的java.util.concurrent.ThreadPoolExecutor $ Worker.run(未知来源)的runWorker(未知来源)(未知来源)

这是我的代码:

@PostConstruct
public void init() {
    eventBus = EventBusFactory.getDefault().eventBus();
}

我正在使用Primefaces 5.2,Wildfly 8.2.0.final,大气运行时2.4.0-RC3.

我的web.xml配置:

<servlet>
    <servlet-name>Push Servlet</servlet-name>
    <servlet-class>org.primefaces.push.PushServlet</servlet-class>
</servlet>
<servlet-mapping>
    <servlet-name>Push Servlet</servlet-name>
    <url-pattern>/primepush/*</url-pattern>
</servlet-mapping>

Answer 1

显然EventBusFactory.getDefault()返回null.将PrimeFaces升级到5.2后可能会出现此问题,并在此处进行了讨论.尝试加载PushServlet启动以进行正确的初始化:

<servlet>
    <servlet-name>Push Servlet</servlet-name>
    <servlet-class>org.primefaces.push.PushServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>