Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jspwiki-dev@incubator.apache.org
Message-ID: <204158842.1233907919635.JavaMail.jira@brutus>
Date: Fri, 6 Feb 2009 00:11:59 -0800 (PST)
From: "Janne Jalkanen (JIRA)" <jira@apache.org>
To: jspwiki-dev@incubator.apache.org
Subject: [jira] Commented: (JSPWIKI-476) Export Tool GUI-Discussion
In-Reply-To: <1445384281.1233069539574.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JSPWIKI-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671043#action_12671043 ] 

Janne Jalkanen commented on JSPWIKI-476:
----------------------------------------

Actually, we were only talking about exporting here - for 3.0, it's the job of the JCR repository to take care of consistency during import, so we don't have to care about it.

However, your scenario would not work, because JSPWiki would prevent the user from saving modified PageTwo, and call an error.  Or, alternatively, the import of PageTwo would fail, because the user has it locked.  We do have page-level locking, remember :-)

In addition, since references are recalculated upon saving, there would be no difference between the above scenario and if someone went ahead and edited PageTwo *after* the import.  The contents would be the same.

> 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.