You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Timothy Ward (Created) (JIRA)" <ji...@apache.org> on 2012/02/02 09:55:54 UTC
[jira] [Created] (ARIES-821) Allow mixtures of interfaces and
classes in proxys
Allow mixtures of interfaces and classes in proxys
--------------------------------------------------
Key: ARIES-821
URL: https://issues.apache.org/jira/browse/ARIES-821
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ARIES-821) Allow mixtures of interfaces and
classes in proxys
Posted by "Timothy Ward (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Ward resolved ARIES-821.
--------------------------------
Resolution: Fixed
> Allow mixtures of interfaces and classes in proxys
> --------------------------------------------------
>
> Key: ARIES-821
> URL: https://issues.apache.org/jira/browse/ARIES-821
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (ARIES-821) Allow mixtures of interfaces and
classes in proxys
Posted by "Timothy Ward (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Ward closed ARIES-821.
------------------------------
> Allow mixtures of interfaces and classes in proxys
> --------------------------------------------------
>
> Key: ARIES-821
> URL: https://issues.apache.org/jira/browse/ARIES-821
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira