[
https://issues.apache.org/jira/browse/DELTASPIKE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755689#comment-13755689
]
Mark Struberg commented on DELTASPIKE-405:
------------------------------------------
{quote}
Incorrect. This case is handled by the fourth bullet in CDI 1.0
{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.
And thus we (both OWB and Weld-1.x filled this gap by providing standard JVM
behaviour.
a.assignableTo(b) != b.assignableTo(a)
got me?
{quote}
Let me remind you that it was you who initiated this change in CDI 1.1
{quote}
Yes, and if you look at what I wrote in https://issues.jboss.org/browse/CDI-304
then you will see that I was always aiming at a solution similar to what the
JVM does: if there is an exact match, then take this, otherwise take the
'nearest' boundary match way up to unbound.
Of course you can blame me that I didn't review the changes to this section
which were done a few days before the PFD. I'm aware that there were 1000
things to be done for the CDI spec in those days and having such an issue slip
through is as normal as drinking tee. This is no blame-game, the sole intention
is how we could possibly fix this issue.
There is no doubt that we need this functionality. OmniFaces faced the same
issue in weld-2.0. This is basically a non-backward compat change to CDI 1.0
and we should clean it up in a MR of the spec.
It is funny that for Weld-2.0 adding the (unbound!) <T> works. But this seems
actually against the CDI 1.1 spec and also is prevented by the TCK (this TCK
test is actually the reason why we 'broke' owb-1.2.1...)
> 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
