On Jan 8, 2009, at 9:53 AM, Gavin King wrote:
On Fri, Jan 9, 2009 at 4:38 AM, Scott Ferguson
<ferg(a)caucho.com>
wrote:
> First, this capability should be implemented as a general Bridge
> defined in
> javax.webbeans.spi.Bridge and define the JavaEE capabilities in
> terms of the
> underlying Bridge. (Similar in logic to Bean but a different point
> in the
> configuration lifecycle.) That would improve modularity and allow an
> eventual migration of the Bridge ownership to the individual JavaEE
> specs in
> a later version.
Hrm, I don't get your comment about configuration lifecycle. Surely
this Bridge would just be a subtype of Bean?
I don't understand what we need it for.
I feel like Bean already provides sufficient pluggability...
The actual Bridge SPI can be put off until JavaEE 7 (when I'd expect
the other JSRs to control their Bridges). As long as webbeans spec
isn't trapped by overspecification, i.e. the spec is logically
consistent with a future underlying Bridge, it doesn't need to be
explicitly defined now.
-- Scott
> Second, the JavaEE annotation types should be defined in their own
> namespace
> for modularity and consistency, not the WebBeans namespace.
>
> <xsql:DataSource xmlns:xsql="urn:java:javax.sql">
> <ann:Resource xmlns:ann="urn:java:javax.annotation">
> ...
> </ann:...>
>
> <my:Foo xmlns:my="urn:java:com.foo.my">
> <ejb:EJB xmlns:ejb="urn:java:javax.ejb">
>
> <jms:Queue xmlns:jms="urn:java:javax.jms">
> ...
I'm OK with that if others are.
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org