You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Ondrej Zizka <oz...@redhat.com> on 2014/04/23 16:14:46 UTC
Wicket + CDI, in JBoss EAP / WildFly
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 instance!
Until seam-conversation-weld is added as dependency.
See https://bugzilla.redhat.com/show_bug.cgi?id=1087471 .
I remember this was the way to go when I created the quickstart,
and it seems to be until now:
http://apache-wicket.1842946.n4.nabble.com/CDI-upgrade-to-1-1-td4658579.html
Is that correct? Or anything new so we could get rid of Seam dependency?
Thanks,
Ondra
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket + CDI, in JBoss EAP / WildFly
Posted by Martijn Dashorst <ma...@gmail.com>.
Which "The Wicket quick start for Wildfly" are you talking about?
Martijn
On Wed, Apr 23, 2014 at 4:14 PM, Ondrej Zizka <oz...@redhat.com> wrote:
> 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
> instance!
>
> Until seam-conversation-weld is added as dependency.
> See https://bugzilla.redhat.com/show_bug.cgi?id=1087471 .
>
> I remember this was the way to go when I created the quickstart,
> and it seems to be until now:
> http://apache-wicket.1842946.n4.nabble.com/CDI-upgrade-to-1-1-td4658579.html
>
> Is that correct? Or anything new so we could get rid of Seam dependency?
>
> Thanks,
> Ondra
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Wicket + CDI, in JBoss EAP / WildFly
Posted by Martin Grigorov <mg...@apache.org>.
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 need SEAM as dependency.
Martin Grigorov
Wicket Training and Consulting
On Wed, Apr 23, 2014 at 5:24 PM, Sande Gilda <sg...@redhat.com> wrote:
> 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 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 <oz...@redhat.com> wrote:
>
>> 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
>> instance!
>>
>> Until seam-conversation-weld is added as dependency.
>> See https://bugzilla.redhat.com/show_bug.cgi?id=1087471 .
>>
>> I remember this was the way to go when I created the quickstart,
>> and it seems to be until now:
>>
>> http://apache-wicket.1842946.n4.nabble.com/CDI-upgrade-to-1-1-td4658579.html
>>
>> Is that correct? Or anything new so we could get rid of Seam dependency?
>>
>> Thanks,
>> Ondra
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
Re: Wicket + CDI, in JBoss EAP / WildFly
Posted by Sande Gilda <sg...@redhat.com>.
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 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 <ozizka@redhat.com
> <ma...@redhat.com>> wrote:
>
> 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 instance!
>
> Until seam-conversation-weld is added as dependency.
> See https://bugzilla.redhat.com/show_bug.cgi?id=1087471 .
>
> I remember this was the way to go when I created the quickstart,
> and it seems to be until now:
> http://apache-wicket.1842946.n4.nabble.com/CDI-upgrade-to-1-1-td4658579.html
>
> Is that correct? Or anything new so we could get rid of Seam
> dependency?
>
> Thanks,
> Ondra
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> <ma...@wicket.apache.org>
> For additional commands, e-mail: users-help@wicket.apache.org
> <ma...@wicket.apache.org>
>
>
Re: Wicket + CDI, in JBoss EAP / WildFly
Posted by Martin Grigorov <mg...@apache.org>.
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 <oz...@redhat.com> wrote:
> 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
> instance!
>
> Until seam-conversation-weld is added as dependency.
> See https://bugzilla.redhat.com/show_bug.cgi?id=1087471 .
>
> I remember this was the way to go when I created the quickstart,
> and it seems to be until now:
> http://apache-wicket.1842946.n4.nabble.com/CDI-upgrade-to-
> 1-1-td4658579.html
>
> Is that correct? Or anything new so we could get rid of Seam dependency?
>
> Thanks,
> Ondra
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>