[JBoss JIRA] Created: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
9:56 a.m.
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
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
8:28 a.m.
New subject: [JBoss JIRA] Updated: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch updated DNA-548:
------------------------------
Priority: Blocker (was: Major)
These are blockers for the release.
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
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
2:36 p.m.
New subject: [JBoss JIRA] Commented: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-548:
-----------------------------------
The ExecutionContext serves as the universal mechanism by which the DNA code knows the
context in which operations are performed, and is available to the connectors that process
the requests, the session that creates the requests, and the Observation system that
post-processes the (complete) requests. The JcrRepository.login(...) method always
creates a new ExecutionContext via the ExecutionContext.with(...), which means that every
JcrSession implementation has a unique ExecutionContext. Therefore, if we add a unique
identifier to the ExecutionContext, that identifier would correspond to the Session
instance.
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
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
2:41 p.m.
New subject: [JBoss JIRA] Resolved: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch resolved DNA-548.
-------------------------------
Resolution: Done
Assignee: Randall Hauch
Added this identifier (a stringified UUID) to the ExecutionContext, and adds a
'contextId' to the Changes class. Then, the RequestProcessor was changed to set
the context ID for the Changes object that it creates.
Marking as resolved.
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
12:59 p.m.
New subject: [JBoss JIRA] Reopened: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Dan Florian reopened DNA-548:
-----------------------------
Reopening since the JcrSession.sessionId() is not matching up with the
Changes.getContextId().
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
1:05 p.m.
New subject: [JBoss JIRA] Commented: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
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
1:41 p.m.
New subject: [JBoss JIRA] Commented: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-548:
-----------------------------------
Changed JcrWorkspace, JcrSession, and WorkspaceLockManager so that they use
ExecutionContext more consistently. JcrWorkspace and JcrSession both share the exact same
ExecutionContext instance, while WorkspaceLockManager was changed to expect the JcrSession
in most of its methods so the lock manager can use the JcrSession's ExecutionContext
in its operations. (The latter also has the advantage of recording which sessions were
performing the lock operations, since now the session's context is used for all lock
operations.)
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
2:16 p.m.
New subject: [JBoss JIRA] Commented: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-548:
-----------------------------------
Found a few more cases where we were being inconsistent with ExecutionContext.
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
10:32 a.m.
New subject: [JBoss JIRA] Resolved: (DNA-548) The Session That Graph Changes Originate From Should Be Available To The NetChangeObserver
[
https://jira.jboss.org/jira/browse/DNA-548?page=com.atlassian.jira.plugin...
]
Dan Florian resolved DNA-548.
-----------------------------
Resolution: Done
Session IDs and Changes IDs are matching. Applicable tests are now passing. Marking as
resolved.
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
5969
days inactive
5995
days old
8 comments
2 participants
participants (2)
-
Dan Florian (JIRA) -
Randall Hauch (JIRA)