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 2011/12/08 23:01:40 UTC
[jira] [Created] (ARIES-801) Aries Proxy cannot proxy abstract
classes
Aries Proxy cannot proxy abstract classes
-----------------------------------------
Key: ARIES-801
URL: https://issues.apache.org/jira/browse/ARIES-801
Project: Aries
Issue Type: Bug
Components: Proxy
Affects Versions: 0.4
Reporter: Timothy Ward
Fix For: 0.4
The proxy component is unable to proxy abstract classes. This is just plain silly for the subclassing code, which should already be able to do this trivially and is definitely a bug.
It should be possible to augment the dynamic interface proxy code so that it can extend "woven" abstract classes too, treating any abstract methods as "interface" and simply setting the superclass properly. Because the interface generation code extends the existing weaving code this is effectively the same as loading and weaving a real concrete subclass that has zero length implementations of the abstract methods.
Interestingly it should also be possible to add interfaces to these dynamically generated woven subclasses. I'm not sure whether this will be useful or not, but we should get it for free.
--
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] [Assigned] (ARIES-801) Aries Proxy cannot proxy abstract
classes
Posted by "Timothy Ward (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Ward reassigned ARIES-801:
----------------------------------
Assignee: Timothy Ward
> Aries Proxy cannot proxy abstract classes
> -----------------------------------------
>
> Key: ARIES-801
> URL: https://issues.apache.org/jira/browse/ARIES-801
> Project: Aries
> Issue Type: Bug
> Components: Proxy
> Affects Versions: 0.4
> Reporter: Timothy Ward
> Assignee: Timothy Ward
> Fix For: 0.4
>
>
> The proxy component is unable to proxy abstract classes. This is just plain silly for the subclassing code, which should already be able to do this trivially and is definitely a bug.
> It should be possible to augment the dynamic interface proxy code so that it can extend "woven" abstract classes too, treating any abstract methods as "interface" and simply setting the superclass properly. Because the interface generation code extends the existing weaving code this is effectively the same as loading and weaving a real concrete subclass that has zero length implementations of the abstract methods.
> Interestingly it should also be possible to add interfaces to these dynamically generated woven subclasses. I'm not sure whether this will be useful or not, but we should get it for free.
--
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-801) Aries Proxy cannot proxy abstract
classes
Posted by "Timothy Ward (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Ward resolved ARIES-801.
--------------------------------
Resolution: Fixed
Added to trunk with tests. Will fix any bugs as/when they are found
> Aries Proxy cannot proxy abstract classes
> -----------------------------------------
>
> Key: ARIES-801
> URL: https://issues.apache.org/jira/browse/ARIES-801
> Project: Aries
> Issue Type: Bug
> Components: Proxy
> Affects Versions: 0.4
> Reporter: Timothy Ward
> Assignee: Timothy Ward
> Fix For: 0.4
>
>
> The proxy component is unable to proxy abstract classes. This is just plain silly for the subclassing code, which should already be able to do this trivially and is definitely a bug.
> It should be possible to augment the dynamic interface proxy code so that it can extend "woven" abstract classes too, treating any abstract methods as "interface" and simply setting the superclass properly. Because the interface generation code extends the existing weaving code this is effectively the same as loading and weaving a real concrete subclass that has zero length implementations of the abstract methods.
> Interestingly it should also be possible to add interfaces to these dynamically generated woven subclasses. I'm not sure whether this will be useful or not, but we should get it for free.
--
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