[weld-issues] [JBoss JIRA] (WELD-1052) Unproxyable bean type check too strict

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Sun Jan 15 03:49:19 EST 2012


    [ https://issues.jboss.org/browse/WELD-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659419#comment-12659419 ] 

Jozef Hartinger commented on WELD-1052:
---------------------------------------

org.jboss.jsr299.tck.tests.context.passivating.broken.nonPassivationCapableProducerField.NonPassivationCapableProducerFieldTest
and
org.jboss.jsr299.tck.tests.context.passivating.broken.nonPassivationCapableProducerMethod.NonPassivationCapableProducerMethodTest

are affected.

                
> Unproxyable bean type check too strict
> --------------------------------------
>
>                 Key: WELD-1052
>                 URL: https://issues.jboss.org/browse/WELD-1052
>             Project: Weld
>          Issue Type: Bug
>          Components: Proxies
>    Affects Versions: 1.1.5.Final
>            Reporter: Jozef Hartinger
>            Assignee: Jozef Hartinger
>             Fix For: 2.0.0.Alpha2
>
>
> According to the specification, a deployment that contains the following bean:
> {code:JAVA}
> public interface FooInterface {
> }
> @ApplicationScoped
> public final class Foo implements FooInterface {
> }
> {code}
> is valid as long as there is no injection point injecting Foo directly.
> The following injection point is valid:
> {code:JAVA}
> @Inject
> private FooInterface foo;
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list