[
https://jira.jboss.org/jira/browse/JBAOP-653?page=com.atlassian.jira.plug...
]
Flavia Rainone closed JBAOP-653.
--------------------------------
Resolution: Done
The nested lock structure has been removed. As I said in a previous talk with Kabir, there
is currently no need to create several lock layers, as the write operations will occur
seldomly. A single lock for all domain levels is a simpler solution that is enough for
now.
Replace ClassifiedBindingAndPointcutCollection lock by AOPLock
--------------------------------------------------------------
Key: JBAOP-653
URL:
https://jira.jboss.org/jira/browse/JBAOP-653
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR17
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Fix For: 2.0.0.GA
The lock of ClassifiedBindingAndPointcutCollection is also being used to orchestrate
actions that don't involve the collection. We need, then, to replace this lock by an
lock independent from the Collection, using the AOPLock class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira