On Sun, Apr 11, 2010 at 10:42 PM, Stuart Douglas <
stuart(a)baileyroberts.com.au> wrote:
I don't particularly like the idea of @Veto being an
@Alternative
stereotype, I think it should veto the bean. Also there is not really that
much difference between typing @Veto and @Alternative anyway, and
@Alternative is clearer as it is part of the spec.
Also implementing @Veto as a stereotype would prevent the bean being
specialized in seam-xml, as seam-xml would apply the @Veto stereotype to the
configured bean.
Good points. I'm not sure why I thought making it an @Alternative was the
right approach. Now that I think about it more, it doesn't make much sense.
I am still interested in having a declarative veto mechanism built-in
somewhere.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen