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 <marco.wittev...@gmail.com > > > 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: > > > > <artifactId>wicket-core</artifactId> > > <artifactId>wicket-auth-roles</artifactId> > > <artifactId>wicket-extensions</artifactId> > > <artifactId>wicket-cdi</artifactId> > > > > Marco > > >
