Hi David! _Which_ of the 4 @ManagedBean classes are you talking of? ;)
I'd prefer to drop all of them altogether :D Really, the one from JSF doesn't make much sense in the future since it is very likely that the JSF-2.2 EG will deprecate it. The one from JSR-317 is a zombie since it was born (3 days before the spec went final...). It is not even used by the RI itself (glassfish). The others are zombies too imo ... LieGrue, strub --- On Fri, 6/10/11, David Blevins <[email protected]> wrote: > From: David Blevins <[email protected]> > Subject: Re: Examples - CDI > To: [email protected] > Date: Friday, June 10, 2011, 12:19 AM > > On Jun 9, 2011, at 4:16 PM, Ranga S wrote: > > > Thanks! > > I tried using the createEJBContainer construct, but it > complains about "not finding any modules to deploy" when I > run it. > > Add a src/main/resources/META-INF/beans.xml file. > That should do the trick. CDI spec requires users to > have a beans.xml even if it is an empty file. > > That said the EJB spec does not require an xml file so we > end up having to scan everything anyway. So we could > probably get it to work without the empty file. > > We're currently just looking for EJB annotations + > @ManagedBean to determine if it is a module of interest, but > we could easily expand that. > > Anyway, for now try with the extra xml file and give a > shout if you run into any issues. > > > -David > >
