[
https://issues.apache.org/jira/browse/WICKET-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg reassigned WICKET-4951:
-------------------------------------
Assignee: Igor Vaynberg
> Wicket-cdi and OpenWebBeans 1.1.x incompatibility
> -------------------------------------------------
>
> Key: WICKET-4951
> URL: https://issues.apache.org/jira/browse/WICKET-4951
> Project: Wicket
> Issue Type: Wish
> Components: wicket-cdi
> Affects Versions: 6.3.0, 6.4.0
> Environment: OpenWebBeans 1.1.x (TomEE 1.5.1)
> Reporter: Dominik Drzewiecki
> Assignee: Igor Vaynberg
> Priority: Minor
>
> It is not particularly Wicket-CDI fault to not support the latest
> OpenWebBeans, but rather seam-conversation-owb-3.0.0.Final, thus this issue
> is reported as a "wish". Seam-conversation-owb-3.0.0 depends on ancient
> OpenWebBeans version, although I've seen some activity in its git
> repositories
> (https://github.com/seam/conversation/commit/a5f2e3f42829f8405e6bee6caab43fd034e5be81)
> and 3.2.0 Snapshots deployed to jboss maven repo
> (https://repository.jboss.org/nexus/content/groups/public/org/jboss/seam/conversation/seam-conversation-owb/3.2.0-SNAPSHOT/)
> seem to depend on OWB 1.1.3. It seems that ConversationManager.getInstance()
> is no longer there which results in the following stacktrace when run on
> tomee 1.5.1 or tomcat + OWB 1.1.7:
> SEVERE: Servlet.service() for servlet [default] in context with path
> [/wcjs-web] threw exception [Filter execution threw an exception] with root
> cause
> java.lang.NoSuchMethodError:
> org.apache.webbeans.conversation.ConversationManager.getInstance()Lorg/apache/webbeans/conversation/ConversationManager;
> at
> org.jboss.seam.conversation.plugins.openwebbeans.OpenWebBeansSeamConversationManager.doActivate(OpenWebBeansSeamConversationManager.java:41)
> at
> org.jboss.seam.conversation.plugins.openwebbeans.OpenWebBeansHttpSeamConversationContext.doActivate(OpenWebBeansHttpSeamConversationContext.java:44)
> at
> org.jboss.seam.conversation.api.AbstractSeamConversationContext.activate(AbstractSeamConversationContext.java:54)
> at
> org.apache.wicket.cdi.CdiContainer.activateConversationalContext(CdiContainer.java:94)
> at
> org.apache.wicket.cdi.ConversationPropagator.activateConversationIfNeeded(ConversationPropagator.java:147)
> at
> org.apache.wicket.cdi.ConversationPropagator.onRequestHandlerResolved(ConversationPropagator.java:123)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:155)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:151)
> at
> org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection.onRequestHandlerResolved(RequestCycleListenerCollection.java:150)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:155)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:151)
> at
> org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection.onRequestHandlerResolved(RequestCycleListenerCollection.java:150)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:155)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection$5.notify(RequestCycleListenerCollection.java:151)
> at
> org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80)
> at
> org.apache.wicket.request.cycle.RequestCycleListenerCollection.onRequestHandlerResolved(RequestCycleListenerCollection.java:150)
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:253)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:211)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:282)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:244)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:267)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45)
> at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> We can either wait till the 3.2.0.Final gets cut, force dependency to
> 3.2.0-SNAPSHOT and provide jboss snapshot repository definition in our poms
> or influence somehow that 3.1.1 release be prepared.
--
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
