[seam-dev] Xml module and preventing bean installation

[Pete Muir]

Sounds like a good idea to me.

On 12 Apr 2010, at 04:06, Stuart Douglas wrote:

> @XmlConfigured currently does exactly that (just veto's the bean in ProcessAnnotatedType event). 
> 
> I would be happy to get rid of @XmlConfigured and replace it with @Veto in weld-extensions, if only to remove the need to create a seam-xml-api package with a single annotation in it.
> 
> Stuart
> ________________________________________
> From: Dan Allen [dan.j.allen at gmail.com]
> Sent: Monday, 12 April 2010 1:00 PM
> To: Stuart Douglas
> Cc: seam-dev at lists.jboss.org
> Subject: Re: [seam-dev] Xml module and preventing bean installation
> 
> On Sun, Apr 11, 2010 at 10:42 PM, Stuart Douglas <stuart at baileyroberts.com.au<mailto:stuart at 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
> 
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev