[
https://issues.apache.org/jira/browse/SLING-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927099#comment-17927099
]
Julian Reschke commented on SLING-12657:
----------------------------------------
Yes. And that actually was the cause why we had to back out a change in Oak
before the 1.76.0 release, as there wasn't sufficient time to fix components
having this problem.
> JcrBase: ProxyRepository implements JackrabbitRepository
> --------------------------------------------------------
>
> Key: SLING-12657
> URL: https://issues.apache.org/jira/browse/SLING-12657
> Project: Sling
> Issue Type: Bug
> Components: JCR
> Reporter: Julian Reschke
> Priority: Major
>
> ...but that interface is of type "provider".
> See [https://cqdump.joerghoh.de/tag/providertype/] and
> [https://github.com/apache/jackrabbit-oak/blob/1939b6c15a1db13222c52e677ea48fdd7424bfb3/oak-jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitRepository.java#L28.]
> Any update to JackrabbitRepository (IMHO) will cause strange runtime
> behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
