That's just how I roll! :) it's a learning exercise for me. I started a cdi integration project long ago and it got lost in the shuffle On Nov 16, 2011 3:42 PM, "Igor Vaynberg" <igor.vaynb...@gmail.com> wrote:
> why would you write your own when one is already there? > > -igor > > On Wed, Nov 16, 2011 at 12:37 PM, James Carman > <ja...@carmanconsulting.com> wrote: > > On Nov 16, 2011 11:49 AM, "Igor Vaynberg" <igor.vaynb...@gmail.com> > wrote: > >> > >> On Wed, Nov 16, 2011 at 3:49 AM, James Carman > >> <ja...@carmanconsulting.com> wrote: > >> > The only thing "external" is the conversation management stuff from > >> > Seam, it looks like. The user would have to make sure they include > >> > the container-specific "adapter" code on the classpath > >> > (org.jboss.seam.conversation:seam-conversation-weld for example) for > >> > their CDI container. > >> > >> yes. this will go away once cdi 1.1 is release which provides the > >> conversation scope api > >> > > > > This will be great! Do they have an eta? For now I'll write my own > > abstraction similar to your CdiContainer > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
