[
https://jira.jboss.org/jira/browse/CDITCK-84?page=com.atlassian.jira.plug...
]
Marius Bogoevici commented on CDITCK-84:
----------------------------------------
(continuing from above)
So, there is no producer in the case above - although in other situations the problem is
created by producers, as in:
org.jboss.jsr299.tck.tests.implementation.producer.field.definition.ProducerFieldDefinitionTest
(FunnelWeaver)
org.jboss.jsr299.tck.tests.implementation.producer.method.definition.ProducerMethodDefinitionTest
(FunnelWeaver as well)
The whole background of the discussion is to be found here:
http://lists.jboss.org/pipermail/weld-dev/2009-December/002025.html
Producer field and producer method tests that use generics contain
ambiguous definitions
----------------------------------------------------------------------------------------
Key: CDITCK-84
URL:
https://jira.jboss.org/jira/browse/CDITCK-84
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.GA
Reporter: Marius Bogoevici
Assignee: Marius Bogoevici
Fix For: 1.1.0.CR1
For example org.jboss.jsr299.tck.tests.lookup.typesafe.resolution.ResolutionByTypeTest,
where Farmer<ScottishFish> references are to be resolved by both the producer and
the managed bean created from Farmer<T>.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira