[
https://issues.apache.org/jira/browse/OAK-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264736#comment-13264736
]
Jukka Zitting commented on OAK-78:
--
Wrong, the javadoc for the Client class clearly says
Hi,
Last week the first Oakathon (Hackathon for Oak [1]) took place in
Basel. Overall it was a big success. We where able to sort out much of
the basics of Oak and shape the project for the future. The short term
focus was on the features of the upcoming 0.2 release [2] and I think we
can
Hi,
Following up on this commit, since it highlights an issue with how we
manage the lifecycle of pluggable components in Oak.
On Fri, Apr 27, 2012 at 1:50 PM, ju...@apache.org wrote:
Fix initialization order issue with the query index provider.
[...]
private
[
https://issues.apache.org/jira/browse/OAK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13264931#comment-13264931
]
Julian Reschke commented on OAK-6:
--
TCK status 2012-04-30: Tests: 1905, Errors: 223, Failures:
Hi,
My idea here is that any pluggable components passed to a
ContentRepositoryImpl or other core class should be already
initialized or be able to lazily initialize itself when needed.
I understand the concern about the lifecycle, but I would also like to
avoid reading from the repository in
