[
https://issues.apache.org/jira/browse/JCR-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2028:
------------------------
Description:
with jsr 283 the jcr path is defined to consist of a combination of the
following segments
• a name segment, (J, I), where J is a JCR name and I is an integer index
(I ≥ 1).
• an identifier segment, U, where U is a JCR identifier.
• the root segment.
• the self segment.
• the parent segment.
-> the name segment can be in extended or qualified form -> see issue JCR-1712
-> the identifier segment is new for jsr283 and always identifies a node (->
see new method Node.getIdentifier())
Non-standard parts always need to be standardized. Any of the following makes a
path non-standard:
- expanded name segments
- trailing /
- index [1]
Identifier-segments
- get resolved upon being passed to any API calls that take path to an existing
Node
- don't get resolved when being used to create a PATH value object.
Except for PATH values, all jcr paths returned by the API are normalized and
standard, thus never identifier-based.
was:
with jsr 283 the jcr path is defined to consist of a combination of the
following segments
• a name segment, (J, I), where J is a JCR name and I is an integer index
(I ≥ 1).
• an identifier segment, U, where U is a JCR identifier.
• the root segment.
• the self segment.
• the parent segment.
-> the name segment can be in extended or qualified form -> see issue JCR-1712
-> the identifier segment is new for jsr283 and always identifies a node (->
see new method Node.getIdentifier())
> JSR 283: JCR Path
> -----------------
>
> Key: JCR-2028
> URL: https://issues.apache.org/jira/browse/JCR-2028
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: JCR 2.0
> Reporter: angela
>
> with jsr 283 the jcr path is defined to consist of a combination of the
> following segments
> • a name segment, (J, I), where J is a JCR name and I is an integer index
> (I ≥ 1).
> • an identifier segment, U, where U is a JCR identifier.
> • the root segment.
> • the self segment.
> • the parent segment.
> -> the name segment can be in extended or qualified form -> see issue JCR-1712
> -> the identifier segment is new for jsr283 and always identifies a node (->
> see new method Node.getIdentifier())
> Non-standard parts always need to be standardized. Any of the following makes
> a path non-standard:
> - expanded name segments
> - trailing /
> - index [1]
> Identifier-segments
> - get resolved upon being passed to any API calls that take path to an
> existing Node
> - don't get resolved when being used to create a PATH value object.
> Except for PATH values, all jcr paths returned by the API are normalized and
> standard, thus never identifier-based.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
