Got it, thks.
Le 15 sept. 2013 07:32, "Jason Porter" <[email protected]> a écrit :

> It's an ease of use thing. The big thing we're missing (I think) is the
> ability to easily setup @Named lists of entities. Seam 2 @Factory did this
> remarkably well and easily. To do this now (again, I've only glanced
> through the code I think would be responsible for this in the data module)
> you'd need to create a new class for each entity, create a producer and
> listen for the event. It would be great if we could do that all behind the
> scenes for people and expose it simply with an annotation or class or
> something similar.
>
>
> On Sat, Sep 14, 2013 at 12:53 AM, Romain Manni-Bucau
> <[email protected]>wrote:
>
> > Hi
> >
> > I dont get the need, using cdi event + repo looks enough. What do I miss?
> > Le 14 sept. 2013 02:04, "Jason Porter" <[email protected]> a
> écrit :
> >
> > > I was looking at
> > >
> > >
> >
> http://stackoverflow.com/questions/18774025/how-can-i-update-a-collection-that-is-produces-applicationscoped
> > > and
> > > the data module came to my mind. I just did a quick glance through the
> > code
> > > I thought was applicable, but I'm still doubtful it'll actually do
> what I
> > > want. Can someone correct me if the data module will actually do this?
> > >
> > > If not, it sure sounds like a killer feature to implement. We'd need to
> > > create events, probably add some more metadata to it, and possibly
> create
> > > some beans so there's a concrete class, or perhaps some
> > InvocationHandlers.
> > >
> > > --
> > > Jason Porter
> > > http://en.gravatar.com/lightguardjp
> > >
> >
>
>
>
> --
> Jason Porter
> http://en.gravatar.com/lightguardjp
>

Reply via email to