[
https://issues.apache.org/jira/browse/DELTASPIKE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755694#comment-13755694
]
Jozef Hartinger commented on DELTASPIKE-405:
--------------------------------------------
{quote}All the paragraph you refer to define the behaviour for:
"A parameterized bean type is considered assignable to a parameterized required
type if ..."
Do you see any "A non-paramterized or unbound bean type is considered
assignable to a parameterized required type if ..." ? I didn't found such a
clause.{quote}
I do not understand. In you example:
IP: @Inject Stable<Horse>
bean: @Produces <PET> Stable<PET> ..
both the required type and the bean type are parameterized types. Therefore
this spec statement:
"A parameterized bean type is considered assignable to a parameterized required
type if they have identical raw type and
for each parameter the required type parameter is an actual type, the bean type
parameter is a type variable and the actual type is assignable
to the upper bound, if any, of the type variable."
applies to this example and the spec allows it. This is therefore the way
JsfMessage producer should look like.
> producer for JsfMessage<T> does not match CDI-1.1 rules
> --------------------------------------------------------
>
> Key: DELTASPIKE-405
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-405
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
> Affects Versions: 0.4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.5
>
>
> Some containers don't find the JsfMessageProducer as it is of a generic type
> <T>.
--
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
