You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2011/06/12 09:09:53 UTC

[jira] [Created] (OPENEJB-1577) from cdi, a request for a proxy might not have a main interface

from cdi, a request for a proxy might not have a main interface
---------------------------------------------------------------

                 Key: OPENEJB-1577
                 URL: https://issues.apache.org/jira/browse/OPENEJB-1577
             Project: OpenEJB
          Issue Type: Bug
          Components: container system
    Affects Versions: 4.0
            Reporter: David Jencks
            Assignee: David Jencks
             Fix For: 4.0


If you call 

      Bean<?> farmerBean = getCurrentManager().resolve(getCurrentManager().getBeans(FarmerLocal.class,LANDOWNER_LITERAL));
      FarmerLocal farmer = (FarmerLocal) getCurrentManager().getReference(farmerBean, Object.class, getCurrentManager().createCreationalContext(farmerBean));

the Object.class gets fed into CdiPlugin and ProxyInterfaceResolver as the main proxy type.  Obviously this won't work :-).

Solution appears to be for the CdiPlugin to convert this to null and the resolver to ignore a null main interface.

This relates to at least org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (OPENEJB-1577) from cdi, a request for a proxy might not have a main interface

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENEJB-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks resolved OPENEJB-1577.
-----------------------------------

    Resolution: Fixed

rev 1134873

> from cdi, a request for a proxy might not have a main interface
> ---------------------------------------------------------------
>
>                 Key: OPENEJB-1577
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1577
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: container system
>    Affects Versions: 4.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 4.0
>
>
> If you call 
>       Bean<?> farmerBean = getCurrentManager().resolve(getCurrentManager().getBeans(FarmerLocal.class,LANDOWNER_LITERAL));
>       FarmerLocal farmer = (FarmerLocal) getCurrentManager().getReference(farmerBean, Object.class, getCurrentManager().createCreationalContext(farmerBean));
> the Object.class gets fed into CdiPlugin and ProxyInterfaceResolver as the main proxy type.  Obviously this won't work :-).
> Solution appears to be for the CdiPlugin to convert this to null and the resolver to ignore a null main interface.
> This relates to at least org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationIntegrationTest

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira