jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1712) JSR 283: JCR Names
Date Fri, 22 Aug 2008 08:08:44 GMT

    [ https://issues.apache.org/jira/browse/JCR-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624616#action_12624616

angela commented on JCR-1712:

> 1) The name parser should decide on jcr name vs extended name *solely* based on the name
to parse. 
> It may be tempting to query the namespace registry, but this is IMHO an extremely bad

isn't it inconsistent, if an extended jcr-name containing an unknown URI passes the parsing,
while parsing a name with unknown prefix fails (the namespace resolver throws NamespaceException)?

> 2) Edge case: as far as I can tell, the only potential edge cases occur when the first
"{"..."}" pair does not 
>      contain a colon character. However, namespace names should be absolute URIs, and
any absolute 
>     URI (by definition) contains a colon. Thus, just rely on that. People who mint namespace
names that 
>     aren't URIs [...] 

initially i had the parser behaving like that. but i got rid of that limitation due to the
fact, that Jackrabbit currently allows any string to be a namespace URI except for the reserved

> [...] will get what they deserve (in this case, the inability to take advantage of the
new syntax).

i don't agree here.

after all and thinking about it, i am not totally convinced that the improvements suggested
by julian should got into the patch.


> JSR 283: JCR Names
> ------------------
>                 Key: JCR-1712
>                 URL: https://issues.apache.org/jira/browse/JCR-1712
>             Project: Jackrabbit
>          Issue Type: Sub-task
>            Reporter: angela
>         Attachments: JCR-1712_1.diff

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message