The problem is that this would not be a sheet of paper but rather one written with 'i' ;)
* no marker file -> requires to scan ALL classes on the whole classpath * heavily underspecified -> what is this damn thing doing in a PORTABLE way? * interoperability, what's that? how does @ManagedBean work together with CDI, with EJB, with JSF managed beans? My suggestion: go the route OWB took with the BDA (Bean Archive Definition) approach: we optionally support this specified but heavily broken feature. But it is disabled in our default configuration. So just introduce a config which is enabled for the TCK tests, and if someone needs this @ManagedBean support for his project, then he is free to use this config too. But it's disable by default. 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, 11:49 PM > > On Jun 10, 2011, at 3:36 AM, Mark Struberg wrote: > > > 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). > > That one. :) It's required part of the EJB TCK so > Glassfish definitely supports it. > > Technically it was added in April and the spec closed that > December, but you're right in the grand scheme of things it > was really really late. And the spec says next to > nothing. > > Since we have to support it, we might as well have fun with > it. I see a blank sheet of paper we can write anything > on :) > > > -David > > > > --- 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 > >> > >> > >
