Re: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance!
Bas & Edmon: thanks Both suggestions works fine for me. The warning is not shown anymore when i use the wicket-cdi-1.1 module in wicket 8.x or when i use wicket 9.x Op wo 23 mrt. 2022 om 22:08 schreef Emond Papegaaij < emond.papega...@gmail.com>: > Hi Marco, > > Wicket 8 contains 2 CDI integration modules: wicket-cdi for CDI 1.0 and > wicket-cdi-1.1 for CDI 1.1 and up. I don't know what CDI version is > supported by the application servers you mentioned, but CDI 1.0 is rather > old and it's likely your server supports 1.1 or higher. If you wish to stay > at wicket 8.x, you should probably switch to wicket-cdi-1.1. In Wicket 9, > the wicket-cdi module was replaced by wicket-cdi-1.1 and support for CDI > 1.0 was dropped. > > Best regards, > Emond > > On Wed, Mar 23, 2022 at 8:00 AM Marco Witteveen > > wrote: > > > When a Wicket app is starting, i see the following warning in the system > > log of our application servers: > > org.jboss.seam.conversation.spi.SeamConversationContextFactory W No > > matching SeamConversationContext for store type interface > > javax.servlet.http.HttpServletRequest, using NOOP instance! > > > > This message is also mentioned in posts in 2013/2014 (search for > > SeamConversationContext) > > but we still get the warning using wicket 8.14.0. > > I've seen the warning in the following application servers: > > > >- IBM WebSphere Application Server 9.0.5.x > >- WebSphere Liberty 22.0.0.1 > >- Open Liberty 22.0.0.1 > > > > We use the following products: > > > >wicket-core > >wicket-auth-roles > >wicket-extensions > >wicket-cdi > > > > Marco > > >
Re: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance!
Hi Marco, Wicket 8 contains 2 CDI integration modules: wicket-cdi for CDI 1.0 and wicket-cdi-1.1 for CDI 1.1 and up. I don't know what CDI version is supported by the application servers you mentioned, but CDI 1.0 is rather old and it's likely your server supports 1.1 or higher. If you wish to stay at wicket 8.x, you should probably switch to wicket-cdi-1.1. In Wicket 9, the wicket-cdi module was replaced by wicket-cdi-1.1 and support for CDI 1.0 was dropped. Best regards, Emond On Wed, Mar 23, 2022 at 8:00 AM Marco Witteveen wrote: > When a Wicket app is starting, i see the following warning in the system > log of our application servers: > org.jboss.seam.conversation.spi.SeamConversationContextFactory W No > matching SeamConversationContext for store type interface > javax.servlet.http.HttpServletRequest, using NOOP instance! > > This message is also mentioned in posts in 2013/2014 (search for > SeamConversationContext) > but we still get the warning using wicket 8.14.0. > I've seen the warning in the following application servers: > >- IBM WebSphere Application Server 9.0.5.x >- WebSphere Liberty 22.0.0.1 >- Open Liberty 22.0.0.1 > > We use the following products: > >wicket-core >wicket-auth-roles >wicket-extensions >wicket-cdi > > Marco >
Re: No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance!
Hi Marco, Referring to https://bugzilla.redhat.com/show_bug.cgi?id=1087471 it seems that the seam conversation library should no longer be referenced from wicket (as indicated in 2014). Looking at the version history of the wicket-cdi pom.xml I see that the dependency on seam conversation was removed in 2018 (with the upgrade to CDI 2): https://github.com/apache/wicket/commit/0f64e1f9e30bb3642805730e2409e9d3ac4ebcea The new version without the seam conversation dependency is wicket 9. Have you tried upgrading to that version? Met vriendelijke groet, Kind regards, Bas Gooren Op 23 maart 2022 bij 07:59:50, Marco Witteveen (marco.wittev...@gmail.com) schreef: When a Wicket app is starting, i see the following warning in the system log of our application servers: org.jboss.seam.conversation.spi.SeamConversationContextFactory W No matching SeamConversationContext for store type interface javax.servlet.http.HttpServletRequest, using NOOP instance! This message is also mentioned in posts in 2013/2014 (search for SeamConversationContext) but we still get the warning using wicket 8.14.0. I've seen the warning in the following application servers: - IBM WebSphere Application Server 9.0.5.x - WebSphere Liberty 22.0.0.1 - Open Liberty 22.0.0.1 We use the following products: wicket-core wicket-auth-roles wicket-extensions wicket-cdi Marco
