Re: [seam-dev] Module reviews

Currently it is: "java.lang", "java.util", "javax.annotation", "javax.inject", "javax.enterprise.inject", "javax.enterprise.context", "javax.enterprise.event", "javax.decorator", "javax.interceptor", Should the root namespace for seam-xml be changed to http://java.sun.com/xml/ns/javaee? I did not use this originally for portability reasons, as other CDI implementations might not like having 'foreign' elements in this namespace in beans.xml.

Stuart On 14/06/2010, at 4:43 PM, Gavin King wrote: > On Mon, Jun 14, 2010 at 8:21 AM, Stuart Douglas > <stuart(a)baileyroberts.com.au&gt; wrote: > >>> --------- >>> Seam XML >>> --------- >>> >>> * CDI annotations need to come from the CDI namespace, not the Seam namespace. For example: >>> >>> <s:Qualifier /> or <s:Specializes /> -> <cdi:Qualifier /> or <cdi:Specializes /> >> >> What namespace is <cdi: bound to? http://java.sun.com/xml/ns/javaee? >> >> If so should I dump the seam namespace entirely, or just move the annotations into a different namespace? > > > Things that are annotations or types from the CDI/EE packages > javax.enterprise.inject, javax.inject, etc, should all live in the > default namespace. Not quite sure what it should be called, but the > spec used to say: > > The Java EE namespace urn:java:ee represents the following packages: > > • java.lang > • java.util > • javax.annotation > • javax.enterprise.inject > • javax.enterprise.context > • javax.interceptor > • javax.decorator > • javax.enterprise.event > • javax.ejb > • javax.persistence > • javax.xml.ws > • javax.jms > • javax.sql > > Now, for what we're doing, that list is probably a bit long and could > be trimmed. > > -- > Gavin King > gavin.king(a)gmail.com > http://in.relation.to/Bloggers/Gavin > http://hibernate.org > http://seamframework.org