You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2009/09/02 11:58:32 UTC
[jira] Created: (JCR-2288)
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that
namespace URI's are registered
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
------------------------------------------------------------------------------------------------------
Key: JCR-2288
URL: https://issues.apache.org/jira/browse/JCR-2288
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-spi-commons
Reporter: Stefan Guggisberg
according to JCR 2.0, "3.4.3.4 Parsing Lexical Paths":
<quote>
An otherwise valid path containing an expanded name with an unregistered
namespace URI will always resolve into a valid internal representation of a path
</quote>
the current implementation assumes that namespace URIs encountered in
expanded form names are registered, otherwise the name is treated as
qualified name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (JCR-2288)
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that
namespace URI's are registered
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755927#action_12755927 ]
angela edited comment on JCR-2288 at 9/16/09 1:05 AM:
------------------------------------------------------
i consider this to be part of JCR-1564 which should address the modified, more flexiable namespace handling.
was (Author: anchela):
i consider this part to be part of JCR-1564 which should address the modified, more flexiable namespace handling.
> o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
> ------------------------------------------------------------------------------------------------------
>
> Key: JCR-2288
> URL: https://issues.apache.org/jira/browse/JCR-2288
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi-commons
> Reporter: Stefan Guggisberg
>
> according to JCR 2.0, "3.4.3.4 Parsing Lexical Paths":
> <quote>
> An otherwise valid path containing an expanded name with an unregistered
> namespace URI will always resolve into a valid internal representation of a path
> </quote>
> the current implementation assumes that namespace URIs encountered in
> expanded form names are registered, otherwise the name is treated as
> qualified name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2288)
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that
namespace URI's are registered
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755927#action_12755927 ]
angela commented on JCR-2288:
-----------------------------
i consider this part to be part of JCR-1564 which should address the modified, more flexiable namespace handling.
> o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
> ------------------------------------------------------------------------------------------------------
>
> Key: JCR-2288
> URL: https://issues.apache.org/jira/browse/JCR-2288
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi-commons
> Reporter: Stefan Guggisberg
>
> according to JCR 2.0, "3.4.3.4 Parsing Lexical Paths":
> <quote>
> An otherwise valid path containing an expanded name with an unregistered
> namespace URI will always resolve into a valid internal representation of a path
> </quote>
> the current implementation assumes that namespace URIs encountered in
> expanded form names are registered, otherwise the name is treated as
> qualified name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2288)
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that
namespace URI's are registered
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755941#action_12755941 ]
Stefan Guggisberg commented on JCR-2288:
----------------------------------------
> i consider this to be part of JCR-1564 which should address the modified, more flexiable namespace handling.
i don't agree. NameParser should IMO not rely on the namespace registry, static analysis should be sufficient (see also JCR-2275).
> o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
> ------------------------------------------------------------------------------------------------------
>
> Key: JCR-2288
> URL: https://issues.apache.org/jira/browse/JCR-2288
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi-commons
> Reporter: Stefan Guggisberg
>
> according to JCR 2.0, "3.4.3.4 Parsing Lexical Paths":
> <quote>
> An otherwise valid path containing an expanded name with an unregistered
> namespace URI will always resolve into a valid internal representation of a path
> </quote>
> the current implementation assumes that namespace URIs encountered in
> expanded form names are registered, otherwise the name is treated as
> qualified name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2288)
o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that
namespace URI's are registered
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2288.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha11
Assignee: Jukka Zitting
Fixed in revision 815745. URI prefixes of the form {} and {x:y} (and {internal} for Jackrabbit compatibility) are now accepted as valid without further namespace checks. This follows the name parsing rules from JCR 2.0 and the relaxed namespace handling mechanism adopted in JCR-1564.
The following corner cases had to be adjusted:
* "{prefix}name" no longer maps to ("prefix","name") but to ("","{prefix}name")
* "{/jackrabbit/}abc" is no longer a valid name, regardless of namespace mappings
* "{abc}" is now a valid local name
> o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
> ------------------------------------------------------------------------------------------------------
>
> Key: JCR-2288
> URL: https://issues.apache.org/jira/browse/JCR-2288
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi-commons
> Reporter: Stefan Guggisberg
> Assignee: Jukka Zitting
> Fix For: 2.0-alpha11
>
>
> according to JCR 2.0, "3.4.3.4 Parsing Lexical Paths":
> <quote>
> An otherwise valid path containing an expanded name with an unregistered
> namespace URI will always resolve into a valid internal representation of a path
> </quote>
> the current implementation assumes that namespace URIs encountered in
> expanded form names are registered, otherwise the name is treated as
> qualified name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.