[
https://issues.apache.org/jira/browse/JSPWIKI-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670441#action_12670441
]
Harry Metske commented on JSPWIKI-476:
--------------------------------------
Let me describe a possible migration scenario:
1. You have your good old wiki running with a classical repo
2. You have installed and configured your brand new and shiny JCR based wiki
3. Then you want to test this new thing and use your existing data
4. You go to your Exporter running in the old wiki and export everything, you
don't need any locking or whatsoever
5. Import the xml file into the new JCR wiki, and test a lot
6. you probably repeat 4,5 a couple of times.
7. you finally reached the point that you are confident the new wiki works
fine, and you want to switch over
8. you then do a final export
9. now you have to be sure that your users don't edit any pages anymore in the
old repo, either by a lock, or by just stopping the old wiki
10. do your final import and redirect your users to the new wiki
If you can afford downtime this scenario is just fine, and you probably don't
need locking.
If not, you might need a time-slot where your wiki is in RO-mode, while you do
your final export/import, and eventually (network)switch to your new wiki or
something like that.
I am very biased by my daily work working with financial/transactional systems,
so maybe Janne is right and we should start with no locking at all, or just
give some error messages during export telling that you are exporting locked
pages.
Let's keep it simple in the first place, we can always make things more
complicated in the future :-)
> 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.
