[
https://issues.apache.org/jira/browse/JSPWIKI-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670689#action_12670689
]
Janne Jalkanen commented on JSPWIKI-476:
----------------------------------------
I don't believe that you do need it. Think about it logically: Assume a
repository with three pages:
PageOne
PageTwo
PageThree
Now, when the export is done, it is done one page at a time, like this:
Export PageOne
Export PageTwo
Export PageThree
There are four possible places where modification can be done:
1) Modifications done before export (=normal situation)
MODIFY PageTwo
Export PageOne
Export PageTwo
Export PageThree
2)
Export PageOne
MODIFY PageTwo
Export PageTwo
Export PageThree
3)
Export PageOne
Export PageTwo
MODIFY PageTwo
Export PageThree
4) (LOCK ALL, no modifications possible)
Export PageOne
Export PageTwo
Export PageThree
MODIFY PageTwo
Let us mark the modified PageTwo with PageTwo'. Therefore, the possible end
results of the repository are
Cases 1 & 2:
PageOne
PageTwo'
PageThree
Cases 3&4:
PageOne
PageTwo
PageThree
We can also argue that there is no difference between these two end results,
since case 1 is any situation in which modification is done outside of the
export process - which is equivalent to case 4. Therefore, all these results
end up in exactly the same exported data, regardless of whether we have
repository-level locking or not. This is possible because *there are no
interdependencies between the pages*.
This can be easily extended then to importing as well, which is logically not
at all different from someone just editing a lot of pages repeatedly in a row.
> Export Tool GUI-Discussion
> --------------------------
>
> Key: JSPWIKI-476
> URL: https://issues.apache.org/jira/browse/JSPWIKI-476
> Project: JSPWiki
> Issue Type: Sub-task
> Components: Core & storage
> Reporter: Olaf Kaus
> Attachments: Export-Implementation-V1.jpg, Export.jpg,
> ExportRunning.jpg
>
>
> I attached a proposal how the export gui could look.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
