You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/08/20 14:43:30 UTC
[jira] Created: (JCR-1068)
NamespaceRegistryTest.testRegisterNamespace test assumptions
NamespaceRegistryTest.testRegisterNamespace test assumptions
------------------------------------------------------------
Key: JCR-1068
URL: https://issues.apache.org/jira/browse/JCR-1068
Project: Jackrabbit
Issue Type: Bug
Components: JCR TCK
Reporter: Julian Reschke
NamespaceRegistryTest.testRegisterNamespace() makes the assumption that it is possible to create arbitrarily nodes inside the root folder.
This is not required to be the case.
Proposal:
- get the name of the test node from the config, and
- use a property rather than a child node for the test (as far as I can tell, many repositories will not allow node names in namespaces other than the empty one).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1068)
NamespaceRegistryTest.testRegisterNamespace test assumptions
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1068:
-------------------------------
Affects Version/s: 1.2.1
1.2.2
1.2.3
1.3
1.3.1
Fix Version/s: 1.3.2
Merged to the 1.3 branch in revision 577852.
> NamespaceRegistryTest.testRegisterNamespace test assumptions
> ------------------------------------------------------------
>
> Key: JCR-1068
> URL: https://issues.apache.org/jira/browse/JCR-1068
> Project: Jackrabbit
> Issue Type: Bug
> Components: JCR TCK
> Affects Versions: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 1.3.2
>
>
> NamespaceRegistryTest.testRegisterNamespace() makes the assumption that it is possible to create arbitrarily nodes inside the root folder.
> This is not required to be the case.
> Proposal:
> - get the name of the test node from the config, and
> - use a property rather than a child node for the test (as far as I can tell, many repositories will not allow node names in namespaces other than the empty one).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1068)
NamespaceRegistryTest.testRegisterNamespace test assumptions
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-1068.
---------------------------------
Resolution: Fixed
Fixed with revision 568259.
> NamespaceRegistryTest.testRegisterNamespace test assumptions
> ------------------------------------------------------------
>
> Key: JCR-1068
> URL: https://issues.apache.org/jira/browse/JCR-1068
> Project: Jackrabbit
> Issue Type: Bug
> Components: JCR TCK
> Reporter: Julian Reschke
> Assignee: Julian Reschke
>
> NamespaceRegistryTest.testRegisterNamespace() makes the assumption that it is possible to create arbitrarily nodes inside the root folder.
> This is not required to be the case.
> Proposal:
> - get the name of the test node from the config, and
> - use a property rather than a child node for the test (as far as I can tell, many repositories will not allow node names in namespaces other than the empty one).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-1068)
NamespaceRegistryTest.testRegisterNamespace test assumptions
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reassigned JCR-1068:
-----------------------------------
Assignee: Julian Reschke
> NamespaceRegistryTest.testRegisterNamespace test assumptions
> ------------------------------------------------------------
>
> Key: JCR-1068
> URL: https://issues.apache.org/jira/browse/JCR-1068
> Project: Jackrabbit
> Issue Type: Bug
> Components: JCR TCK
> Reporter: Julian Reschke
> Assignee: Julian Reschke
>
> NamespaceRegistryTest.testRegisterNamespace() makes the assumption that it is possible to create arbitrarily nodes inside the root folder.
> This is not required to be the case.
> Proposal:
> - get the name of the test node from the config, and
> - use a property rather than a child node for the test (as far as I can tell, many repositories will not allow node names in namespaces other than the empty one).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1068)
NamespaceRegistryTest.testRegisterNamespace test assumptions
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521570 ]
Julian Reschke commented on JCR-1068:
-------------------------------------
Modified proposal: when creating a child node fails, try a property instead. This requires no new config, and let's my implementation pass this test.
> NamespaceRegistryTest.testRegisterNamespace test assumptions
> ------------------------------------------------------------
>
> Key: JCR-1068
> URL: https://issues.apache.org/jira/browse/JCR-1068
> Project: Jackrabbit
> Issue Type: Bug
> Components: JCR TCK
> Reporter: Julian Reschke
> Assignee: Julian Reschke
>
> NamespaceRegistryTest.testRegisterNamespace() makes the assumption that it is possible to create arbitrarily nodes inside the root folder.
> This is not required to be the case.
> Proposal:
> - get the name of the test node from the config, and
> - use a property rather than a child node for the test (as far as I can tell, many repositories will not allow node names in namespaces other than the empty one).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.