Hi, I put that one up. The need is genuine, here is some background. Apache Sling uses a content repository to store its content. You can think of it like a file system but its a lot more sophisticated than that. The standard content repository is Apache Jackrabbit. Version 1.x and 2.x of Apache Jackrabbit were focused on delivering blisteringly fast read access to content in deep content hierarchies where 99% of the activity was read and 1% was write. It does that outstandingly well. Time has moved on, the web has become more social and applications typically have higher levels of write acces. Content trees have become more user generated and hence are often flatter with few levels and millions of children.
Apache Oak is the next generation of Apache Jackrabbit which aims to support much higher levels of write, and much wider flatter content hierarchies. It has also been designed to support cloud like deployments on NoSQL infrastructure There is support for storage on MongoDB already and other backends are almost certainly possible. Where Jackrabbit 2.x was capable of being deployed in small clusters, Oak should be suitable for large clusters. For Apache Sling to use Apache Oak the Apache Jackrabbit server component has been replaced with an Apache Oak version. Fortunately all the projects mentioned interact constantly and so the basics of this all work. What hasn't been done yet is to bring up an Sling instance running on Oak and run the 100s of Sling integration tests against that instance. If that can be achieved it will create a high level of confidence that Sling will run on Oak. As of today, here is what works: An instance of Sling running on Oak that starts up and accepts requests using Basic http authentication.[1] An initial attempt at getting the integration testing framework running, which almost starts. The GSoC project will need to: Make the integration test framework run. Identify tests that fail. Fix tests that fail by providing patches to Sling or to Apache Oak. (Optionally) write some tests that exercise some of the features of Oak (high levels of write, large numbers of children). If you want to take up this challenge you are going to need to be willing to learn about OSGi and you will have to be prepared on interact with both the Sling and Jackrabbit/Oak communities, as most of the solutions to problems you find will be in the community, such is Apache! Ian 1 http://svn.apache.org/repos/asf/sling/whiteboard/ieb/oak/ (there is a commit pending here, within the hour). On 30 April 2013 08:38, Marcus Santos <[email protected]> wrote: > Hi everyone, > > I'm interested to contribute on the project "Test and Fix Apache Oak > Integration with Sling" under GSOC. How can I talk with the mentor to know > more about it and expose my doubts? > > Best regards, > Marcus Santos >
