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: <artifactId>wicket-core</artifactId> <artifactId>wicket-auth-roles</artifactId> <artifactId>wicket-extensions</artifactId> <artifactId>wicket-cdi</artifactId> Marco
