jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2288) o.a.jackrabbit.spi.commons.conversion.NameParser should not assume that namespace URI's are registered
Date Wed, 16 Sep 2009 12:57:57 GMT

     [ 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.


Mime
View raw message