the easiest way in this case is a formal vote about @Veto vs @Exclude vs @Unmanaged/@NotManaged
regards, gerhard 2011/12/30 Dan Allen <dan.j.al...@gmail.com> > On Wed, Dec 28, 2011 at 11:55, Marius Bogoevici > <marius.bogoev...@gmail.com>wrote: > > > I suggested @Unmanaged (or even @NotManaged, or anything that refers to > > "class as a managed bean" in the spirit of 3.1.1). Overall, I think that > > @Unmanaged is a better fit, for the reasons I explained previously. I > think > > that renaming is not such a big issue, in the light of a DeltaSpike > > migration. > > > > I agree. The best suggestion yet, esp since we seem to be at an impasse > between @Veto and @Exclude. > > I think that @NotManaged reads better than @Unmanaged, but I would be happy > with either one. > > -Dan > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://google.com/profiles/dan.j.allen > http://mojavelinux.com > http://mojavelinux.com/seaminaction >
