You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2006/08/02 15:23:14 UTC
[jira] Resolved: (JCR-504) TCK: DocumentViewImportTest does not
call refresh after direct-to-workspace import
[ http://issues.apache.org/jira/browse/JCR-504?page=all ]
Marcel Reutegger resolved JCR-504.
----------------------------------
Fix Version/s: 1.1
Resolution: Fixed
Fixed as suggested in revision: 427974
Thank you for reporting this issue.
> TCK: DocumentViewImportTest does not call refresh after direct-to-workspace import
> ----------------------------------------------------------------------------------
>
> Key: JCR-504
> URL: http://issues.apache.org/jira/browse/JCR-504
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: David Pitfield
> Fix For: 1.1
>
>
> After performing a direct-to-workspace import, the test does not call refresh to ensure the transient layer doesn't contain stale data.
> Proposal: call refresh(false) after performing direct-to-workspace imports.
> --- DocumentViewImportTest.java (revision 422074)
> +++ DocumentViewImportTest.java (working copy)
> @@ -106,6 +106,12 @@
> SAXException, NotExecutableException {
>
> importXML(target, createSimpleDocument(), uuidBehaviour, withWorkspace);
> +
> + if (withWorkspace)
> + {
> + session.refresh(false);
> + }
> +
> performTests();
> }
>
> @@ -127,6 +133,12 @@
> SAXException, IOException, NotExecutableException {
>
> importWithHandler(target, createSimpleDocument(), uuidBehaviour, withWorkspace);
> +
> + if (withWorkspace)
> + {
> + session.refresh(false);
> + }
> +
> performTests();
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira