You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Matthias Wessendorf <ma...@apache.org> on 2009/12/31 14:02:51 UTC
story behind the @Current
Hey,
the @Current has been removed from the CDI spec.
We now use @Inject @Default instead.
Does one know the story behind removing @Current?
Thx,
Matthias
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: story behind the @Current
Posted by Matthias Wessendorf <ma...@apache.org>.
On Thu, Dec 31, 2009 at 2:16 PM, Mark Struberg <st...@yahoo.de> wrote:
> @Current was only needed to explicitly declare a class member as getting injected. This has basically been replaced with @Inject (it has a slightly different meaning, but basically serves the same need).
>
ah, ok. I wonder if you guys should (or could) provide a OWB specific
@Current (which does @Inject @Default)
> But I also have a quick question :)
>
> Is trinidad/branches/trinidad-2.0.x already facelets-2 aware?
yap. at least it compiles against JSF 2.0:
See more on rev 824901:
http://svn.apache.org/viewvc?view=revision&revision=824901
A quick look at a (random) tag handler shows that:
http://svn.apache.org/viewvc/myfaces/trinidad/branches/trinidad-2.0.x/trinidad-impl/src/main/java/org/apache/myfaces/trinidadinternal/facelets/AccessKeyPropertyTagRule.java?r1=823088&r2=824901&pathrev=824901&diff_format=h
If there are questions, concerns, suggestions or what ever, please
raise them on dev@myfaces.a.o.
Thx,
Matthias
PS: Happy new Year (und guten rutsch!)
> I currently _really_ have a lot of pain because the old facelets-1 taglibs simply do not work with JSF-2, and by switching back to facelets-1, I loose a lot of the really cool features like JSR-303 validation :/
>
> LieGrue,
> strub
>
>
> --- On Thu, 12/31/09, Matthias Wessendorf <ma...@apache.org> wrote:
>
>> From: Matthias Wessendorf <ma...@apache.org>
>> Subject: story behind the @Current
>> To: dev@openwebbeans.apache.org
>> Date: Thursday, December 31, 2009, 2:02 PM
>> Hey,
>>
>> the @Current has been removed from the CDI spec.
>> We now use @Inject @Default instead.
>>
>> Does one know the story behind removing @Current?
>>
>> Thx,
>> Matthias
>>
>> -Matthias
>>
>> --
>> 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: story behind the @Current
Posted by Mark Struberg <st...@yahoo.de>.
@Current was only needed to explicitly declare a class member as getting injected. This has basically been replaced with @Inject (it has a slightly different meaning, but basically serves the same need).
But I also have a quick question :)
Is trinidad/branches/trinidad-2.0.x already facelets-2 aware?
I currently _really_ have a lot of pain because the old facelets-1 taglibs simply do not work with JSF-2, and by switching back to facelets-1, I loose a lot of the really cool features like JSR-303 validation :/
LieGrue,
strub
--- On Thu, 12/31/09, Matthias Wessendorf <ma...@apache.org> wrote:
> From: Matthias Wessendorf <ma...@apache.org>
> Subject: story behind the @Current
> To: dev@openwebbeans.apache.org
> Date: Thursday, December 31, 2009, 2:02 PM
> Hey,
>
> the @Current has been removed from the CDI spec.
> We now use @Inject @Default instead.
>
> Does one know the story behind removing @Current?
>
> Thx,
> Matthias
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>