You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/03/26 22:11:15 UTC
[jira] [Updated] (CLOUDSTACK-1795) Customize AOP to fully support
legacy CloudStack @DB and @ActionEvent semantics
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti updated CLOUDSTACK-1795:
-----------------------------------------
Fix Version/s: 4.1.0
> Customize AOP to fully support legacy CloudStack @DB and @ActionEvent semantics
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1795
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Kelven Yang
> Assignee: Kelven Yang
> Priority: Blocker
> Fix For: 4.1.0
>
>
> Implementation of Spring AOP is based on object-proxy-ing mode. In legacy CloudStack code, @ActionEvent assumes the ability of being able to intercept method calls in nested mode.
> We need to use a customized AOP to fully support the semantics requirement posted by legacy CloudStack code. This needs to be fixed before the formal 4.1/4.2 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira