The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit 2.8.6. The release is available for download at:
https://jackrabbit.apache.org/jcr/downloads.html#v2.8
See the full release notes below for details about this release:
Release Notes -- Apache Jackrabbit
the slides of the adaptTo() 2017 conference in berlin are now online - 24 talks
plus lightning talks, 200 participants.
you find the slides and code samples here:
https://adapt.to/2017/schedule
and some images... (more to follow)
https://adapt.to/2017/en/conference/gallery.html
this year we
Eventually managed to understand the root cause using the Felix
ScrService and printing out component information.
See https://issues.apache.org/jira/browse/OAK-6736 .
Thanks,
Robert
On Wed, 2017-09-27 at 19:27 +0530, Chetan Mehrotra wrote:
> You need to do two changes
>
> 1. Set
You need to do two changes
1. Set ds.loglevel=4 as you have done
2. Configure logger corresponding to bundle symbolic name to trace
level. Do it for the bundles you are interested in
> BTW, did you ever try to set up the web console? I would give it a shot.
Not here but the standalone example
Hi Robert,
The unit-test.log should give details about which bundle is starting
and which components are activated like [1]. For the error you are
seeing it means RepositoryManager is not getting activated for some
reason (may be some missing dependency).
So we would need to analyze from OSGi
Hi,
I am trying out some changes to the OSGi annotations based on Julian's
work and I'm getting test failures in oak-pojosr, for instance
[INFO] Running org.apache.jackrabbit.oak.run.osgi.RepositoryClosedTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
61.084 s <<<
Hi,
As Chetan mentioned JCR sessions are synchronous. However IIUC, you are
wrapping operations on sessions into futures in your code. So I would
guess you would have to use the future API to determine the state of the
wrapped operation (e.g. via a completion handler).
Michael
On 26.09.17
