Hi,
I wonder if this is the only functionality in the Oak codebase, which
requires on this. I would assume that other functionality relies also such
a functionality, and I wonder how they solved it.
Of course if this an unresolved issue at the moment, and many mbeans are
not working in SlingStarte
Hi Julian,
According to your recommendation, I've created a Jira issue for that and
submitted a pull request. Could you please review the pull request?
Jira: https://issues.apache.org/jira/browse/SLING-12848
Pull request:
https://github.com/apache/sling-org-apache-sling-jcr-oak-server/pull/15
On
Hi Herman
I think the request is reasonable and the diff you shared looks fine.
Can you please create a JIRA issue to track this improvement, update
your commits to reference the JIRA ID and submit a PR? Thanks!
Regards
Julian
On Mon, 30 Jun 2025 at 09:31, Herman Ciechanowiec
wrote:
>
> Hi Jör
Hi
I think the request to register Oak's internal API ContentRepository
object as a service is reasonable. Particularly if the MBean
registration depends on the presence of this service.
Regards
Julian
On Mon, 30 Jun 2025 at 07:49, Jörg Hoh wrote:
>
> Hi Herman,
>
> can you outline what problem
Hi Jörg,
Thank you for the quick reply. Here is a more detailed explanation of the
problem we are trying to solve:
The core issue is that the
`org.apache.jackrabbit.oak.spi.security.authentication.external.impl.jmx.SynchronizationMBean`
for Oak's external authentication is unavailable in a standa
Hi Herman,
can you outline what problem you are trying to solve?
Isn't the SlingRepository service (
https://sling.apache.org/apidocs/sling13/org/apache/sling/jcr/api/SlingRepository.html)
providing exactly the same functionality as the Oak ContentRepository ((
https://github.com/apache/jackrabbi