[MAGNOLIA-1225] HierarchyManager - inconsistency in using workspace and session Created: 21/Nov/06  Updated: 18/Jul/14  Resolved: 12/May/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0 Final
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sameer Charles Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-1263 links are sometimes resolved wrongly ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Some core methods like move and copy uses direct workspace writing as oppose to all other core API which
uses transient (session) space so that you have full control over transaction and error handling

It would be good to expose seperate methods for direct workspace operations.



 Comments   
Comment by Magnolia International [ 01/Feb/07 ]

This is also maybe the reason why move and copy methods need a path relative to the root node of the workspace, but not starting with /, while methods like isExist require a leading /

(confusion increases with ContentUtil.createPath for instance, which accepts a leading / but ignores it )

Comment by Sameer Charles [ 15/Feb/07 ]

We need to fix this soon because of "possible" inconsitent system session updates.

Comment by Sameer Charles [ 01/Mar/07 ]

moving it for 3.1 sine It needs more changes and deeper understanding of the related Issues

Comment by Magnolia International [ 07/Nov/07 ]

We need to figure this out for 3.1 (potentially postponing changes, but at least settling on the resolution)

Comment by Magnolia International [ 22/Nov/07 ]

Nothing has been done on this matter. We'll look into this in a future version.

Generated at Mon Feb 12 03:24:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.