[
https://issues.jboss.org/browse/CDI-304?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-304:
----------------------------------
Mark, I don't follow your comment. What do you mean with "ambiguous
situations"? If you have multiple producer methods "which map to different
generic types of the same base type" each PM has a different bean type (e.g.
Foo<String> and Foo<Integer>), or not?
I also found this sentence in 3.3 Producer methods:
"If a producer method return type contains a wildcard type parameter the container
automatically detects the problem and treats it as a definition error."
This seems a little bit inconsistent to me. We would allow raw return type and disallow
type with wildcard... but there is probably some reason I don't see.
Clarify Producers for injection into generic types
--------------------------------------------------
Key: CDI-304
URL:
https://issues.jboss.org/browse/CDI-304
Project: CDI Specification Issues
Issue Type: Clarification
Components: Beans
Affects Versions: 1.1.PRD
Reporter: Mark Struberg
Fix For: 1.1 (Proposed)
There is a discussion over in DeltaSpike whether an injection point
{code}
@Inject
private JsfMessage<SomeMessageClass>;
{code}
with a producer method
{code}
@Produces @Dependent
JsfMessage createMessage(InjectionPoint ip)
{code}
5.2 imo only defines the other way around. Having a raw type at the injection point and a
parameterized producer method.
We should define how this is intended to work.
Please note that the producer above works in all existing containers so far but not in
Weld2-beta1.
Here is the link to the DS issue:
https://issues.apache.org/jira/browse/DELTASPIKE-295
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira