[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-548:
-----------------------------------
The WorkspaceLockManager, JcrSession, and JcrWorkspace all use slightly different
ExecutionContexts. Now that IDs are associated with the context, we need to be more
diligent about using the right one.
The Session That Graph Changes Originate From Should Be Available To
The NetChangeObserver
------------------------------------------------------------------------------------------
Key: DNA-548
URL:
https://jira.jboss.org/jira/browse/DNA-548
Project: DNA
Issue Type: Task
Components: JCR
Affects Versions: 0.6
Reporter: Dan Florian
Assignee: Randall Hauch
Priority: Blocker
Fix For: 0.7
There is no way for the ObservationManager to obtain the session from the
NetChanges/Changes/ChangeRequest objects. The session identifier is needed to implement
the event notification of the ObservationManager. Specifically, listeners are registered
with a "noLocal" flag indicating if they want or don't want to receive
events from the session that they are registered in.
--
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