You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "Michael Dürig (Created JIRA)" <ji...@apache.org> on 2012/04/11 17:25:20 UTC
[jira] [Created] (OAK-61) Implement JCR path handling
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
[jira] [Commented] (OAK-61) Implement JCR path handling
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290039#comment-13290039 ]
Julian Reschke commented on OAK-61:
-----------------------------------
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
[jira] [Commented] (OAK-61) Implement JCR path handling
Posted by "Michael Dürig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258668#comment-13258668 ]
Michael Dürig commented on OAK-61:
----------------------------------
In revision r1328538 I committed a prove of concept implementation for mapping qualified names, expanded names and microkernel names. The mappings are not persisted yet but only kept in memory.
> 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
[jira] [Commented] (OAK-61) Implement JCR path handling
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285696#comment-13285696 ]
Julian Reschke commented on OAK-61:
-----------------------------------
The current approach should be extended to:
# split the *mapping* operation from the *resolution* operation; *mapping* should not affect index handling ({{foo[1]}}), so that methods that need to check for valid names to be added (such as in {{addNode}}) can do so
# optimize the case where nothing needs to be rewritten (for instance, when the JCR path does not contain expanded names, and there is no session-local prefix remapping)
> 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
[jira] [Comment Edited] (OAK-61) Implement JCR path handling
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (OAK-61) Implement JCR path handling
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OAK-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved OAK-61.
-------------------------------
Resolution: Fixed
I believe all functionality is there now; thus anything that's not working right now should be treated as separate bug.
> 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