CoreSession does not contain any state besides the Session (connection to the database), but this session is closed at transaction end so in effect there's no point in keeping a CoreSession beyond a transaction boundary.
This allows up to clean up many things related to management of session ids.
- depends on
-
NXP-11551 Allow merged contributions for the repository config
- Resolved
-
NXP-14140 Make CoreSession thread-safe
- Resolved
-
NXP-13113 Clean up use of DocumentModelIterator
- Resolved
-
NXP-13286 Clean up use of CoreInstance.getSession(sid) and DocumentModel.getSessionId()
- Resolved
-
NXP-13326 Clean up WebDAV code
- Resolved
-
NXP-14122 Make EventService deal with tx end, not CoreSession
- Resolved