[webbeans-dev] Re: Rough draft proposal for resource injection
Gavin King
gavin at hibernate.org
Wed Jan 14 03:00:15 EST 2009
Yes, I'm just wondering what is said about serializability of the
injected references...
On Wed, Jan 14, 2009 at 6:50 PM, Gurkan Erdogdu <gurkanerdogdu at yahoo.com> wrote:
> Hi;
>
> As far as I know, with the *JMS exception*, Java EE container injects the
> artifacts : Java EE Resources, Persistent Context, Persistent Unit, EJB and
> WebService when developer use the applicable annotations that are defined in
> its respective specifications.
>
> I think that addition of the extra layer may not be necessary for these type
> of resources.
>
> Thanks;
>
> /Gurkan
>
> ________________________________
> From: Gavin King <gavin at hibernate.org>
> To: Java Community Process JSR #299 Expert List <JSR-299-EG at jcp.org>; Matt
> Drees <matt.drees at gmail.com>; Scott Ferguson <ferg at caucho.com>; WebBeans
> <webbeans-dev at lists.jboss.org>
> Sent: Wednesday, January 14, 2009 3:04:32 AM
> Subject: [webbeans-dev] Re: Rough draft proposal for resource injection
>
> I have still received very little feedback on this proposal...
>
> On Fri, Jan 9, 2009 at 9:44 PM, Gavin King <gavin at hibernate.org> wrote:
>> 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 at 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 at 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 at gmail.com
>>>> http://in.relation.to/Bloggers/Gavin
>>>> http://hibernate.org
>>>> http://seamframework.org
>>>>
>>>
>>>
>>>
>>> --
>>> Gavin King
>>> gavin.king at gmail.com
>>> http://in.relation.to/Bloggers/Gavin
>>> http://hibernate.org
>>> http://seamframework.org
>>>
>>
>>
>>
>> --
>> Gavin King
>> gavin.king at gmail.com
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>>
>
>
>
> --
> Gavin King
> gavin.king at gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>
>
--
Gavin King
gavin.king at gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
More information about the weld-dev
mailing list