[ 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 -- 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

[ http://jira.jboss.com/jira/browse/JBAOP-517?page=comments#action_12401799 ] Kabir Khan commented on JBAOP-517: ---------------------------------- Unless this gets done for CR8 (the first public release since CR3) it will not work with EJB 3 in AS4.x -- 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

[ http://jira.jboss.com/jira/browse/JBAOP-517?page=all ] Kabir Khan closed JBAOP-517. ---------------------------- Resolution: Done This had already been done. I verified against the ejb3 testsuite on 4.0.4.GA today, so we should be fine. -- 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