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 2010/08/14 06:50:16 UTC

[jira] Closed: (OPENEJB-1328) Track which interface a proxy was asked to implement

     [ https://issues.apache.org/jira/browse/OPENEJB-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks closed OPENEJB-1328.
---------------------------------

    Resolution: Fixed

I think this is pretty completely fixed in rev 985428.

We already have a "mainInterface" field in the base proxy class, so I just added a parameter to every method to fill this in from the source.  It might be possible to try to get the main interface first in the list of interfaces but this is apt to cause a lot of reordering of lists which seems harder to understand and slower than just adding another parameter.

One bit I'm uncomfortable about is the difference between the jdk interface proxies and our asm class proxies and the factories that produce them.  Unless we unify these somehow we need a bunch of special code to decide which to use in a few places.

> Track which interface a proxy was asked to implement
> ----------------------------------------------------
>
>                 Key: OPENEJB-1328
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1328
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: ejb31
>    Affects Versions: 3.2
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.2
>
>
> There are several requirements in the 3.1 spec around making sure that the interface that was asked for for a proxy is carefully tracked.  For instance the 3.4.7.x sections explain how this is used in .equals(otherejb).  We don't do this currently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.