aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Ward (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (ARIES-821) Allow mixtures of interfaces and classes in proxys
Date Thu, 02 Feb 2012 10:09:53 GMT


Timothy Ward resolved ARIES-821.

    Resolution: Fixed
> Allow mixtures of interfaces and classes in proxys
> --------------------------------------------------
>                 Key: ARIES-821
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: Proxy
>    Affects Versions: proxy.impl-0.4
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>             Fix For: proxy.impl-0.4
> The new interface proxying code is able to create very fast dynamic proxy classes for
arbitrary sets of interface (like a better JDK proxy). With a small amount of effort we can
also allow this code to specify an arbitrary superclass for the proxy being generated. This
will allow us to generate proxys that add interfaces to the class being proxied.
> This may not sound very useful, but it means a blueprint bean Bar, that extends AbstractFoo,
and implements Baz, can be exposed as an AbstractFoo and a Baz, but not a Bar. This works
even though AbstractFoo does not implement Bar! This is the sort of thing that the blueprint
spec was talking about when it says that beans/references should only expose the methods on
declared interfaces.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message