Yes, this is why it is essential to read the coverage report at the
same time to understand what is being tested.
On 14 Mar 2009, at 23:25, Gurkan Erdogdu wrote:
It is very difficult to understand TCK tests that are written by
others and it gets so much time. So questions are inevitable.
In the mean time, Pete thanks for helping and commenting. After
that, I will attach jira issues for all other my questions.
Cheers;
Gurkan
From: Pete Muir <pmuir(a)redhat.com>
To: Gurkan Erdogdu <gurkanerdogdu(a)yahoo.com>
Cc: webbeans-dev(a)lists.jboss.org
Sent: Sunday, March 15, 2009 1:05:44 AM
Subject: Re: [webbeans-dev] TCK-Test -->
ProducerFieldDefinitionTest#testNonStaticProducerFieldNotInherited
No, this is testing that producer fields aren't inherited by default.
I suggest you read the spec-assertion matched, and reference in the
coverage report
http://snapshots.jboss.org/maven2/org/jboss/jsr299/tck/jsr299-tck-impl/1....
This list really isn't the right place to discuss this - please
either open JIRA issues or forum topics.
On 14 Mar 2009, at 22:53, Gurkan Erdogdu wrote:
> Hi ;
>
> In this test, InfertileChicken is selected for Chicken API type,
because DeploymentType precedence is higher than Chicken. So *egg*
field is called over InfertileChicken.(Field parent instance API
Type = Chicken and Binding Type = @Current)
>
> But test is contradicted to this. Or any other semantic exist?
>
> @AnotherDeploymentType
> class InfertileChicken extends Chicken
> {
>
> }
>
> class Chicken
> {
>
> @Produces @Foo
> private Egg egg = new Egg(this);
>
> }
>
> Thanks;
>
> Gurkan
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete