jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-61) Implement JCR path handling
Date Wed, 06 Jun 2012 09:22:23 GMT

    [ https://issues.apache.org/jira/browse/OAK-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290039#comment-13290039
] 

Julian Reschke edited comment on OAK-61 at 6/6/12 9:20 AM:
-----------------------------------------------------------

Updated status:

# The mapper now knows whether there are prefix remappings. The conversion code takes advantage
of it (short cutting certain conversions), and we have a few tests for that. However, the
session namespace remapper doesn't provide this information yet (it always says "I have remappings"),
because we need to refactor the prefix handling in SessionImpl for that.
# Refactored the PathParser so that names and indices are handled atomically (needed for:
see below)
# Added a variant of getOakPath that keeps the index information, but, contrary to what was
discussed before, does normalization. This was needed so that code that check the last path
segment (such as addNode()) can conveniently extract the last segment. The new method is currently
only used for addNode(), copy() and move().

If we need a method that does prefix rewriting but no normalization we can add this later
on.
                
      was (Author: reschke):
    Updated status:

# The mapper now knows whether there are prefix remappings. The conversion code takes advantage
of it (short cutting certain conversions), and we have a few tests for that. However, the
session namespace remapper doesn't provide this information yet (it always says "I have remappings"),
because we need to refactor the prefix handling in SessionImpl for that.
# Refactored the PathParser so that names and indices are handled atomically (needed for:
see below)
# Added a variant of getOakPath that keeps the index information, but, contrary to what was
discussed before, does normalization. This was needed so that code that check the last path
segment (such as addNode()) can conveniently extract the last segment. The new method is currently
only used for addNode(), copy() and move().
                  
> Implement JCR path handling
> ---------------------------
>
>                 Key: OAK-61
>                 URL: https://issues.apache.org/jira/browse/OAK-61
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: jcr
>            Reporter: Michael Dürig
>
> This includes:
> - handling paths with full qualified names
> - identifier paths
> - handling remapped name space prefixes
> - validation
> - ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message