You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2010/03/04 10:04:27 UTC
[jira] Created: (JCR-2537) spi2davex: clear uri-lookup after
removing node identified with uniqueID
spi2davex: clear uri-lookup after removing node identified with uniqueID
------------------------------------------------------------------------
Key: JCR-2537
URL: https://issues.apache.org/jira/browse/JCR-2537
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-spi2dav
Affects Versions: 2.0.0
Reporter: angela
Assignee: angela
some test cases of DocumentViewImportTest fail in the setup (line 325 of AbstractImportXmlTest) since the uri resolved from the specified
nodeID still refers to the node removed during the initial import before. this would equally cause problems whenever a referenceable node was
replaced by another node and can easily be fixed by clearing the uri-cache after the removal as it was already done for move.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2537) spi2davex: clear uri-lookup after
removing node identified with uniqueID
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-2537.
-------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
> spi2davex: clear uri-lookup after removing node identified with uniqueID
> ------------------------------------------------------------------------
>
> Key: JCR-2537
> URL: https://issues.apache.org/jira/browse/JCR-2537
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.0.0
> Reporter: angela
> Assignee: angela
> Fix For: 2.0.1
>
>
> some test cases of DocumentViewImportTest fail in the setup (line 325 of AbstractImportXmlTest) since the uri resolved from the specified
> nodeID still refers to the node removed during the initial import before. this would equally cause problems whenever a referenceable node was
> replaced by another node and can easily be fixed by clearing the uri-cache after the removal as it was already done for move.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2537) spi2davex: clear uri-lookup after
removing node identified with uniqueID
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-2537:
------------------------
Fix Version/s: (was: 2.0.1)
2.1.0
> spi2davex: clear uri-lookup after removing node identified with uniqueID
> ------------------------------------------------------------------------
>
> Key: JCR-2537
> URL: https://issues.apache.org/jira/browse/JCR-2537
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.0.0
> Reporter: angela
> Assignee: angela
> Fix For: 2.1.0
>
>
> some test cases of DocumentViewImportTest fail in the setup (line 325 of AbstractImportXmlTest) since the uri resolved from the specified
> nodeID still refers to the node removed during the initial import before. this would equally cause problems whenever a referenceable node was
> replaced by another node and can easily be fixed by clearing the uri-cache after the removal as it was already done for move.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.