[
http://jira.jboss.com/jira/browse/JBAOP-517?page=comments#action_12395617 ]
Kabir Khan commented on JBAOP-517:
----------------------------------
Kabir says:
We might have to maintain that field anyway
Kabir says:
Since EJB 3 in JBoss 4.0.x will be accessing it
Kabir says:
and we want people to be able to upgrade to AOP 2.0 in JBoss 4.0.x
Kabir says:
In fact we will have to maintain it
Kabir says:
Maybe we could make maintaining that field configurable?
Kabir says:
Or if we use JBoss 4.x we know that it must be used, and if using Jboss 5 we know it
isn't used?
Kabir says:
JBoss 4 and 5 have different aspectmanager services, so it could just be a case of
maintaining that from there
Kabir says:
And standalone would not need to use it
Enable Advisor.methodInterceptors field
---------------------------------------
Key: JBAOP-517
URL:
http://jira.jboss.com/jira/browse/JBAOP-517
Project: JBoss AOP
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR3
Reporter: Flavia Rainone
Assigned To: Flavia Rainone
Fix For: 2.0.0.GA
During JBAOP-487 implementation, this field has been disabled.
It needs to be enabled again, since this broke compatiblity with JBoss 4.0.x EJB3.
This task includes also adding tests for that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira