Hi Sande,
Since our Wicket CDI experts didn't answer you I will try.
wicket-cdi module provides integration for CDI 1.0 impls. It requires SEAM
dependencies to provide support for CDI conversations.
wicket-cdi-1.1 provides support for CDI 1.1 impls (e.g. JBoss 8.x, aka
WildFly) and it doesn't
Hi,
the Wicket quickstart for WildFly, when deployed, gives a warning -
WARNING [org.jboss.seam.conversation.spi.SeamConversationContextFactory]
(ServerService Thread Pool -- 48) No matching SeamConversationContext for store
type interface javax.servlet.http.HttpServletRequest, using NOOP
Which The Wicket quick start for Wildfly are you talking about?
Martijn
On Wed, Apr 23, 2014 at 4:14 PM, Ondrej Zizka ozi...@redhat.com wrote:
Hi,
the Wicket quickstart for WildFly, when deployed, gives a warning -
WARNING [org.jboss.seam.conversation.spi.SeamConversationContextFactory]
Hi,
Wicket Quickstart (http://wicket.apache.org/start/quickstart.html) doesn't
use CDI.
Which quickstart do you talk about ?
Which version of wicket-cdi - 1.0 or 1.1 ?
Martin Grigorov
Wicket Training and Consulting
On Wed, Apr 23, 2014 at 5:14 PM, Ondrej Zizka ozi...@redhat.com wrote:
Hi,
Hi Martin,
He's referring to the wicket-war and wickeet-ear quickstarts here:
https://github.com/jboss-developer/jboss-eap-quickstarts
On 04/23/2014 10:20 AM, Martin Grigorov wrote:
Hi,
Wicket Quickstart (http://wicket.apache.org/start/quickstart.html)
doesn't use CDI.
Which quickstart
