4:55 p.m.
Hi;
In test SimpleBeanLifecycleTest # testSpecializedBeanExtendsManagedBean, MountainLion
specializes the Lion so the managed bean with Lion is never resolved.
So getBeans(Lion.class, TAME_LITERAL) returns bean with MountationLion not bean with
Lion.
Therefore assert bean != null; in the test case seems not to be correct!
WDYT?
Thks;
--Gurkan
___________________________________________________________________
Yahoo! Türkiye açıldı! http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
10:30 a.m.
On Sat, 2010-01-09 at 13:55 -0800, Gurkan Erdogdu wrote:
Hi;
In test SimpleBeanLifecycleTest #
testSpecializedBeanExtendsManagedBean, MountainLion specializes the
Lion so the managed bean with Lion is never resolved.
So getBeans(Lion.class, TAME_LITERAL) returns bean with MountationLion
not bean with Lion.
As the test shows, both MountainLion and Lion are returned. There are
no alternatives being used here. It is strictly testing @Specializes
for a managed bean, and as required by the spec, the specializing bean
inherits the @Tame qualifier. That is why both beans are resolved based
on the type and qualifiers specified in the test.
Therefore assert bean != null; in the test case seems not to be
correct!
WDYT?
Thks;
--Gurkan
______________________________________________________________________
Yahoo! Türkiye açıldı!
Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de!
www.yahoo.com.tr
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
10:49 a.m.
Actually, I think due to the late-change we discussed the other day (about what beans are
enabled), this test is wrong - if you look at 5.1.2, you'll see that beans which have
been specialized (in this case Lion) are disabled, and so not returned by getBeans().
Gurkan, you know the drill, please create a CDITCK issue :-)
Thanks!
On 10 Jan 2010, at 15:30, David Allen wrote:
On Sat, 2010-01-09 at 13:55 -0800, Gurkan Erdogdu wrote:
> Hi;
>
> In test SimpleBeanLifecycleTest #
> testSpecializedBeanExtendsManagedBean, MountainLion specializes the
> Lion so the managed bean with Lion is never resolved.
>
> So getBeans(Lion.class, TAME_LITERAL) returns bean with MountationLion
> not bean with Lion.
As the test shows, both MountainLion and Lion are returned. There are
no alternatives being used here. It is strictly testing @Specializes
for a managed bean, and as required by the spec, the specializing bean
inherits the @Tame qualifier. That is why both beans are resolved based
on the type and qualifiers specified in the test.
>
> Therefore assert bean != null; in the test case seems not to be
> correct!
>
> WDYT?
>
> Thks;
>
> --Gurkan
>
>
>
> ______________________________________________________________________
> Yahoo! Türkiye açıldı!
> Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de!
> www.yahoo.com.tr
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
2:48 p.m.
Hi Pete,
I have created issue with https://jira.jboss.org/jira/browse/CDITCK-91
Thks;
--Gurkan
________________________________
From: Pete Muir <pmuir(a)redhat.com>
To: David.Allen(a)acm.org
Cc: Gurkan Erdogdu <gurkanerdogdu(a)yahoo.com>; weld-dev(a)lists.jboss.org
Sent: Sun, January 10, 2010 5:49:37 PM
Subject: Re: [weld-dev] [TCK Related] Question on SimpleBeanLifecycleTest
Actually, I think due to the late-change we discussed the other day (about what beans are
enabled), this test is wrong - if you look at 5.1.2, you'll see that beans which have
been specialized (in this case Lion) are disabled, and so not returned by getBeans().
Gurkan, you know the drill, please create a CDITCK issue :-)
Thanks!
On 10 Jan 2010, at 15:30, David Allen wrote:
On Sat, 2010-01-09 at 13:55 -0800, Gurkan Erdogdu wrote:
> Hi;
>
> In test SimpleBeanLifecycleTest #
> testSpecializedBeanExtendsManagedBean, MountainLion specializes the
> Lion so the managed bean with Lion is never resolved.
>
> So getBeans(Lion.class, TAME_LITERAL) returns bean with MountationLion
> not bean with Lion.
As the test shows, both MountainLion and Lion are returned. There are
no alternatives being used here. It is strictly testing @Specializes
for a managed bean, and as required by the spec, the specializing bean
inherits the @Tame qualifier. That is why both beans are resolved based
on the type and qualifiers specified in the test.
>
> Therefore assert bean != null; in the test case seems not to be
> correct!
>
> WDYT?
>
> Thks;
>
> --Gurkan
>
>
>
> ______________________________________________________________________
> Yahoo! Türkiye açıldı!
> Haber, Ekonomi, Videolar, Oyunlar hepsi Yahoo! Türkiye'de!
> www.yahoo.com.tr
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
___________________________________________________________________
Yahoo! Türkiye açıldı! http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
5218
days inactive
5219
days old
3 comments
3 participants
participants (3)
-
David Allen -
Gurkan Erdogdu -
Pete Muir