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/02/01 17:24:05 UTC
[jira] Created: (JCR-727) NamespaceRegistryTest uses an invalid URI
as namespace URI
NamespaceRegistryTest uses an invalid URI as namespace URI
----------------------------------------------------------
Key: JCR-727
URL: https://issues.apache.org/jira/browse/JCR-727
Project: Jackrabbit
Issue Type: Bug
Components: test
Reporter: Julian Reschke
Priority: Trivial
The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
Suggest to fix by using a proper URI, such as by prefixing with "http://".
A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-727) NamespaceRegistryTest uses an invalid
URI as namespace URI
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469521 ]
Julian Reschke commented on JCR-727:
------------------------------------
Just a nit: "www.apache.org/..." is a relative reference (<http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.4.2>), but not a URI (<http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.3>).
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://".
> A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-727) NamespaceRegistryTest uses an invalid
URI as namespace URI
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473543 ]
Jukka Zitting commented on JCR-727:
-----------------------------------
Thanks for the terminology update! The devil's in the details...
The XML namespace spec says: "An XML namespace is identified by a URI reference [RFC3986]", meaning both full URIs and relative URI references. The current version adds a note that deprecates the use of relative URI references.
The JCR spec somewhat vaguely says: "Namespacing in a content repository is patterned after namespacing in XML. As in XML, the prefix is actually shorthand for the full namespace, which is a URI."
It seems fair to interpret this as meaning that only full URIs are allowed as JCR namespaces.
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://".
> A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-727) NamespaceRegistryTest uses an invalid
URI as namespace URI
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469519 ]
Jukka Zitting commented on JCR-727:
-----------------------------------
> A related question is what our expectation is for JCR implementations. Are they
> allowed to reject something that doesn't parse as a URI according to RFC3986?
I don't recall the JCR spec saying anything about this, but since XML namespace (http://www.w3.org/TR/REC-xml-names/) names are RFC 3986 URIs, I think it would be perfectly OK for a repository implementatino to only allow valid URIs. One concrete benefit of such a policy would be the avoidance of invalid namespace names in XML exports. In fact we may even want to consider enforcing this in Jackrabbit.
PS. The "www.apache.org/..." name can actually be interpreted as a relative URI, and is only deprecated but not strictly prohibited by the current XML namespace spec.
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://".
> A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-727) NamespaceRegistryTest uses an invalid
URI as namespace URI
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-727.
--------------------------------
Resolution: Fixed
Fixed with revision 502263.
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://".
> A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-727) NamespaceRegistryTest uses an invalid URI
as namespace URI
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-727:
------------------------------
Fix Version/s: 1.3
> NamespaceRegistryTest uses an invalid URI as namespace URI
> ----------------------------------------------------------
>
> Key: JCR-727
> URL: https://issues.apache.org/jira/browse/JCR-727
> Project: Jackrabbit
> Issue Type: Bug
> Components: test
> Reporter: Julian Reschke
> Priority: Trivial
> Fix For: 1.3
>
>
> The test cases use "www.apache.org/..." as a namespace URI, but this is not a URI.
> Suggest to fix by using a proper URI, such as by prefixing with "http://".
> A related question is what our expectation is for JCR implementations. Are they allowed to reject something that doesn't parse as a URI according to RFC3986?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.