jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2275) some legal jcr names cause unneccessary server-roundtrips
Date Wed, 26 Aug 2009 09:47:59 GMT

     [ https://issues.apache.org/jira/browse/JCR-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stefan Guggisberg updated JCR-2275:

    Attachment: JCR-2275.patch

a patch for o.a.jackrabbit.spi.commons.conversion,NameParser 
that includes a simple static check of the name in order to 
avoid unneccessary server-roundtrips 

the following names are always considered being qualified jcr names since the would be illegal
expanded form: 
- "{foo}" => empty local name is not allowed 
- "{foo} bar" => leading space in local name is not allowed 

however, the patch causes 2 failures in o.a.jackrabbit.spi.commons.conversion,NameParser;

IMO the failing test cases are questionable and could be fixed.

> some legal jcr names cause unneccessary server-roundtrips 
> ----------------------------------------------------------
>                 Key: JCR-2275
>                 URL: https://issues.apache.org/jira/browse/JCR-2275
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: Stefan Guggisberg
>         Attachments: JCR-2275.patch
> assume the following legal qualified jcr names:
> "{foo}"
> "{foo} bar"
> when items with such names are read from the spi layer, they are first interpreted as
expanded form names.
> a prefix lookup for namespace 'foo' fails and the name is treated as qualified jcr name.
> => depending on the spi implementation, a server-roundtrip is required in order to
determine that 'foo' is not a
> registered namespace. 

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

View raw message