You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Matthias Wessendorf <ma...@apache.org> on 2009/05/05 19:45:05 UTC

Fwd: FYI: javax.inject* standard ...

FYI


---------- Forwarded message ----------
From: Matthias Wessendorf <ma...@apache.org>
Date: Tue, May 5, 2009 at 7:34 PM
Subject: FYI: javax.inject* standard ...
To: openwebbeans-dev@incubator.apache.org
Cc: Pete Muir <pm...@redhat.com>


FYI:
http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html

what does this mean to JSR 299 ?

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: FYI: javax.inject* standard ...

Posted by Simon Lessard <si...@gmail.com>.
I agree, it should have been more abstract to start with, and not depend on
JSF for conversation scope either. Actually, the more I think about it, the
more I think that it should have been JSF extending 299 with conversation
scope through WebBeans custom scope feature and it should have been the same
for EJB 3. Currently it seems to me that the dependency links with JSR-299
are all in the opposite direction that they should have been.

~ Simon


On Tue, May 5, 2009 at 2:02 PM, Simon Lessard <si...@gmail.com>wrote:

> That's true, but I think most JSR-299 impl can run outside JEE environment
> already. Many specs started in EE and ended in SE 1 or 2 version of the SDK
> later.
>
>
> On Tue, May 5, 2009 at 1:57 PM, Matthias Wessendorf <ma...@apache.org>wrote:
>
>> the big failure of the JSR 299 is that it just lives in JavaEE land.
>>
>> Best would have been to introduce a flexible DI API in SE land.
>> This could be extended in all the different profiles. So, 299 could
>> have just been a *consumer* of that flexible DI in order to extend
>> it and add the things that are needed for EJB and all the other EE things.
>>
>> just my $0.02
>>
>> -M
>>
>> On Tue, May 5, 2009 at 7:54 PM, Simon Lessard <si...@gmail.com>
>> wrote:
>> > Weird, it certainly overlaps BIG time, most of what their spec seem to
>> have
>> > is already in JSR-299 too... Maybe I'm missing something...
>> >
>> > On Tue, May 5, 2009 at 1:45 PM, Matthias Wessendorf <ma...@apache.org>
>> > wrote:
>> >>
>> >> FYI
>> >>
>> >>
>> >> ---------- Forwarded message ----------
>> >> From: Matthias Wessendorf <ma...@apache.org>
>> >> Date: Tue, May 5, 2009 at 7:34 PM
>> >> Subject: FYI: javax.inject* standard ...
>> >> To: openwebbeans-dev@incubator.apache.org
>> >> Cc: Pete Muir <pm...@redhat.com>
>> >>
>> >>
>> >> FYI:
>> >> http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html
>> >>
>> >> what does this mean to JSR 299 ?
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> twitter: http://twitter.com/mwessendorf
>> >>
>> >>
>> >>
>> >> --
>> >> Matthias Wessendorf
>> >>
>> >> blog: http://matthiaswessendorf.wordpress.com/
>> >> sessions: http://www.slideshare.net/mwessendorf
>> >> twitter: http://twitter.com/mwessendorf
>> >
>> >
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>

Re: FYI: javax.inject* standard ...

Posted by Simon Lessard <si...@gmail.com>.
That's true, but I think most JSR-299 impl can run outside JEE environment
already. Many specs started in EE and ended in SE 1 or 2 version of the SDK
later.

On Tue, May 5, 2009 at 1:57 PM, Matthias Wessendorf <ma...@apache.org>wrote:

> the big failure of the JSR 299 is that it just lives in JavaEE land.
>
> Best would have been to introduce a flexible DI API in SE land.
> This could be extended in all the different profiles. So, 299 could
> have just been a *consumer* of that flexible DI in order to extend
> it and add the things that are needed for EJB and all the other EE things.
>
> just my $0.02
>
> -M
>
> On Tue, May 5, 2009 at 7:54 PM, Simon Lessard <si...@gmail.com>
> wrote:
> > Weird, it certainly overlaps BIG time, most of what their spec seem to
> have
> > is already in JSR-299 too... Maybe I'm missing something...
> >
> > On Tue, May 5, 2009 at 1:45 PM, Matthias Wessendorf <ma...@apache.org>
> > wrote:
> >>
> >> FYI
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Matthias Wessendorf <ma...@apache.org>
> >> Date: Tue, May 5, 2009 at 7:34 PM
> >> Subject: FYI: javax.inject* standard ...
> >> To: openwebbeans-dev@incubator.apache.org
> >> Cc: Pete Muir <pm...@redhat.com>
> >>
> >>
> >> FYI:
> >> http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html
> >>
> >> what does this mean to JSR 299 ?
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >
> >
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>

Re: FYI: javax.inject* standard ...

Posted by Matthias Wessendorf <ma...@apache.org>.
the big failure of the JSR 299 is that it just lives in JavaEE land.

Best would have been to introduce a flexible DI API in SE land.
This could be extended in all the different profiles. So, 299 could
have just been a *consumer* of that flexible DI in order to extend
it and add the things that are needed for EJB and all the other EE things.

just my $0.02

-M

On Tue, May 5, 2009 at 7:54 PM, Simon Lessard <si...@gmail.com> wrote:
> Weird, it certainly overlaps BIG time, most of what their spec seem to have
> is already in JSR-299 too... Maybe I'm missing something...
>
> On Tue, May 5, 2009 at 1:45 PM, Matthias Wessendorf <ma...@apache.org>
> wrote:
>>
>> FYI
>>
>>
>> ---------- Forwarded message ----------
>> From: Matthias Wessendorf <ma...@apache.org>
>> Date: Tue, May 5, 2009 at 7:34 PM
>> Subject: FYI: javax.inject* standard ...
>> To: openwebbeans-dev@incubator.apache.org
>> Cc: Pete Muir <pm...@redhat.com>
>>
>>
>> FYI:
>> http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html
>>
>> what does this mean to JSR 299 ?
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: FYI: javax.inject* standard ...

Posted by Simon Lessard <si...@gmail.com>.
Weird, it certainly overlaps BIG time, most of what their spec seem to have
is already in JSR-299 too... Maybe I'm missing something...

On Tue, May 5, 2009 at 1:45 PM, Matthias Wessendorf <ma...@apache.org>wrote:

> FYI
>
>
> ---------- Forwarded message ----------
> From: Matthias Wessendorf <ma...@apache.org>
> Date: Tue, May 5, 2009 at 7:34 PM
> Subject: FYI: javax.inject* standard ...
> To: openwebbeans-dev@incubator.apache.org
> Cc: Pete Muir <pm...@redhat.com>
>
>
> FYI:
> http://google-code-updates.blogspot.com/2009/05/javaxinjectinject.html
>
> what does this mean to JSR 299 ?
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>