Now here's a much more complete proposal that also makes the JMS
resource stuff follow the new approach.
Look at the following sections:
3.6
3.7.2
6.8
10.3
Seems to be working out very nicely. I really hope you guys like it.
On Fri, Jan 9, 2009 at 2:24 AM, Gavin King <gavin(a)hibernate.org> wrote:
Here's a second draft (still rough) that incorporates
persistence
contexts and units into the same approach.
On Fri, Jan 9, 2009 at 12:47 AM, Gavin King <gavin(a)hibernate.org> wrote:
> Everyone, please take a look at section 3.6 of this spec draft, which
> defines a proposal for EE resource injection.
>
> Basically, what I've proposed is that web beans would let you rewrite
> the following:
>
> @Resource(mappedName="customerDatabase") Datasource ds;
>
> as:
>
> @CustomerDatabase Datasource ds;
>
> <javaxsql:Datasource>
> <Resource>
> <mappedName>customerDatabase</mappedName>
> </Resource>
> <myapp:CustomerDatabase/>
> </javaxsql:Datasource>
>
> and:
>
> @EJB(ejbLink="somejar#Foo") Foo foo;
>
> as:
>
> @Current Foo foo;
>
> <myapp:Foo>
> <EJB>
> <ejbLink>somejar#Foo</ejbLink>
> </EJB>
> </myapp:Foo>
>
> and:
>
> @WebServiceRef(name="barbar", wsdlLocation="barbarbar") Bar
bar;
>
> as:
>
> @Current Bar bar;
>
> <myapp:Bar>
> <WebServiceRef>
> <name>barbar</name>
> <wsdlLocation>barbarbar</wsdLocation>
> </WebServiceRef>
> </myapp:Bar>
>
> So this proposal is just basically an indirection around the
> pre-existing semantics of Java EE injection, that gives you all the
> nice Web Beans typesafety.
>
> This seems a really nice, easy way to define this stuff, and I love
> how the XML looks.
>
> --
> Gavin King
> gavin.king(a)gmail.com
>
http://in.relation.to/Bloggers/Gavin
>
http://hibernate.org
>
http://seamframework.org
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org