deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jozef Hartinger (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DELTASPIKE-295) JsfMessageProducer createJsfMessage return type should be parametrized
Date Fri, 30 Nov 2012 10:15:59 GMT

    [ https://issues.apache.org/jira/browse/DELTASPIKE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507240#comment-13507240
] 

Jozef Hartinger edited comment on DELTASPIKE-295 at 11/30/12 10:15 AM:
-----------------------------------------------------------------------

CDI 1.0 Section 5.2 Typesafe resolution says:

"Parameterized and raw types are considered to match if they are identical or if the bean
type is assignable to
the required type, as defined in Section 5.2.3, “Assignability of raw and parameterized
types"

The bean type is not identical to the required type nor are these types defined as assignable
 in 5.2.3

I hope introducing the type variable to the producer method won't break other containers as
otherwise we have a problem.
                
      was (Author: jharting):
    CDI 1.0 Section 5.2 Typesafe resolution says:

{quote}Parameterized and raw types are considered to match if they are identical or if the
bean type is assignable to
the required type, as defined in Section 5.2.3, “Assignability of raw and parameterized
types”{quote}

The bean type is not identical to the required type nor are these types defined as assignable
 in 5.2.3

I hope introducing the type variable to the producer method won't break other containers as
otherwise we have a problem.
                  
> JsfMessageProducer createJsfMessage return type should be parametrized
> ----------------------------------------------------------------------
>
>                 Key: DELTASPIKE-295
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-295
>             Project: DeltaSpike
>          Issue Type: Bug
>          Components: JSF-Module
>    Affects Versions: 0.4-incubating
>         Environment: Current 0.4-incubating snapshot, Weld 2.0.0.Beta1
>            Reporter: Marek Schmidt
>             Fix For: 0.4-incubating
>
>
> The 
> {code}
> public JsfMessage createJsfMessage(InjectionPoint injectionPoint)
> {code}
> should probably be
> {code}
> public <T> JsfMessage<T> createJsfMessage(InjectionPoint injectionPoint)
> {code}
> instead.
> The problem manifests itself in Weld 2.0.0.Beta1:
> {noformat}
> Tests in error: 
>   org.apache.deltaspike.test.jsf.impl.message.JsfMessageTest: Could not deploy to container:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jsfMessageTest.war\".WeldService"
=> "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jsfMessageTest.war\".WeldService:
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type
[JsfMessage<UserMessage>] with qualifiers [@Default] at injection point [[BackedAnnotatedField]
@Inject private org.apache.deltaspike.test.jsf.impl.message.beans.JsfMessageBackingBean.msg]"}}
> {noformat}

--
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

Mime
View raw message