[
https://issues.apache.org/jira/browse/OAK-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949469#comment-17949469
]
Konrad Windszus commented on OAK-9584:
--------------------------------------
> the default behavior for what namespace names can be registered we can't
> change (backwards compat)
This is tracked separately in https://issues.apache.org/jira/browse/OAK-11683,
feel free to have a look at its linked PR.
> the behaviors for get/has for all items should be consistent.
I adjusted the title to make it clear that all JCR method taking a name are
affected.
> JCR methods only support qualified names but not expanded names for namespace
> prefix "rep:".
> --------------------------------------------------------------------------------------------
>
> Key: OAK-9584
> URL: https://issues.apache.org/jira/browse/OAK-9584
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 1.40.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> I have a JCR Node which returns
> {{true}} for
> {code}
> node.hasProperty("rep:authorizableId")
> {code} but
> {{false}} for
> {code}
> node.hasProperty("{internal}authorizableId")
> {code}
> According to
> https://docs.adobe.com/content/docs/en/spec/jcr/2.0/3_Repository_Model.html#3.2.6%20Use%20of%20Qualified%20and%20Expanded%20Names
> bq. When a JCR name is passed as an argument to a JCR method it may be in
> either expanded or qualified form.
> this is a violation of the spec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
