Bug 36128 - (2.1 release) Everything should always enlist stores
Summary: (2.1 release) Everything should always enlist stores
Status: NEW
Alias: None
Product: Slide
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.1
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 17:35 UTC by Max Pfingsthorn
Modified: 2005-08-31 05:27 UTC (History)
0 users



Attachments
patch to set forceStoreEnlistment in StructureImpl, LockImpl and ContentImpl (2.08 KB, patch)
2005-08-10 17:36 UTC, Max Pfingsthorn
Details | Diff
update the patch to also edit MacroImpl, affected the COPY method (3.12 KB, patch)
2005-08-31 13:27 UTC, Max Pfingsthorn
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Max Pfingsthorn 2005-08-10 17:35:47 UTC
In creating methods (like PUT, MKCOL), the main transaction is used for creating
resources, but not for checking the credentials and locks later on. This causes
those methods to fail because outside the uncommitted transaction, that resource
doesn't exist yet. Slide gets unusable this way.
The solution seems to be to force the enlistment of stores into the main
transaction. I made a patch which aims to fix these main points of trouble, I
don't know how complete this patch is yet. Testing will take some more time. At
least, you can do MKCOL and PUT again.
This patch is only for the 2.1 release branch. 2.2-dev doesn't seem to have the
problem.
Comment 1 Max Pfingsthorn 2005-08-10 17:36:45 UTC
Created attachment 15997 [details]
patch to set forceStoreEnlistment in StructureImpl, LockImpl and ContentImpl
Comment 2 Max Pfingsthorn 2005-08-31 13:27:42 UTC
Created attachment 16264 [details]
update the patch to also edit MacroImpl, affected the COPY method

After some testing, I found out that the COPY method also failed because of
harmful "readonly" tokens. I added my modifications to MacroImpl in the patch.