Whether you use the new OWBInjector or the CdiInjector (an 1:1 copy of it) is just a matter of backward compat. If you don't need backward compat, then you can certainly use the new OWBInjector.
The more important part is whether you need to store the CreationalContext and do proper cleanup or not... That was the main intention behind removing the inject() method with no CreationalContext parameter. LieGrue, strub ----- Original Message ----- > From: Romain Manni-Bucau <[email protected]> > To: [email protected]; Mark Struberg <[email protected]> > Cc: > Sent: Monday, July 30, 2012 4:15 PM > Subject: Re: OpenEjbContainer CreationalContext handling > > well started to hack on it too > > i don't think we want cdiinjector :p > > - Romain > > > 2012/7/30 Mark Struberg <[email protected]> > >> Well, I'm not sure what you use the OWBInjector for in this case. But > if >> you use it to inject some @Dependent beans on the uppermost level, then you >> will need it to release those beans properly at the end! >> >> >> I didn't mean to drop it but to do some proper cleanup instead :) >> >> >> LieGrue, >> strub >> >> >________________________________ >> > From: Romain Manni-Bucau <[email protected]> >> >To: [email protected]; Mark Struberg <[email protected]> >> >Sent: Monday, July 30, 2012 10:23 AM >> >Subject: Re: OpenEjbContainer CreationalContext handling >> > >> > >> >Hi, >> > >> >yes noticed it too, will remove it. >> > >> >- Romain >> > >> > >> > >> >2012/7/28 Mark Struberg <[email protected]> >> > >> >Hi! >> >> >> >>While applying a fix for the OWBInjector, I found that your >> OpenEjbContainer has a field >> >> >> >>private CreationalContext<Object> creationalContext >> >> >> >> >> >>but this only gets released and never set ^^ >> >> >> >>LieGrue, >> >>strub >> >> >> > >> > >> > >> >
