[
https://issues.apache.org/jira/browse/OAK-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433592#comment-17433592
]
Konrad Windszus commented on OAK-9584:
--------------------------------------
[~mreutegg] proposed using "known.issues" in
https://github.com/apache/jackrabbit-oak/pull/376#issuecomment-937700312. Also
I didn't get any feedback on my question in
https://github.com/apache/jackrabbit-oak/pull/376#issuecomment-947387590.
Therefore I went ahead with this solution.
I am also fine with just using an ignore (although that way it is harder to see
at one glance which known issues are there). [~reschke] Feel free to convert
the test code.
> Node.hasProperty("rep:authorizableId") only supports qualified names but not
> expanded names.
> --------------------------------------------------------------------------------------------
>
> 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
> 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.3.4#803005)
