Pete,
We did not want to mess with the actual current semantics of the
annotation, so for us it only works if you have @Named, managed beans or
EJBs. I think a generalized solution should allow for expressing
dependencies via names, classes and/or component-level annotations
(qualifiers, stereotypes, servlets, ejb types, etc). Basically a
declarative form of BeanManager.getBeans?
Incidentally, what's your thoughts on decoupling
@AfterBegin/_at_AfterCompletion/_at_BeforeCompletion/_at_PostActivate/_at_PrePassivate/_at_Remove.
We don't have those decoupled yet on Resin because they seem tougher to
justify outside the EJB world. Same for the extended persistence scope...
Cheers,
Reza
On 7/10/2011 2:22 PM, Pete Muir wrote:
> I think this is a really good idea, and would fix something people really want in CDI.
>
> One question with @DependsOn - it takes ejb names as attributes, which is something managed beans (especially CDI beans) don't have. Whilst this may be more of an issue for the CDI EG, any ideas on how to handle this?
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1388 / Virus Database: 1516/3754 - Release Date: 07/09/11
>
>
>