Hi all,
out of curiosity, I was wondering if there's any guideline other than
following the API on writing a new MK implementation.
What one should start with, design concepts, experience on known dos,
donts, caveats, etc.
In the past I wanted to play with it a bit but never had time to do
Hi Tommaso,
On Wed, Nov 6, 2013 at 11:31 AM, Tommaso Teofili
tommaso.teof...@gmail.com wrote:
...out of curiosity, I was wondering if there's any guideline other than
following the API on writing a new MK implementation
FWIW, the OAK-784 HBase microkernel code might provide some useful
Hi,
Implementing a complete MK is quite some work. It depends what you want to
do with it. If you want to quickly implement a storage backend that you
can test with Oak, then it might be easier to implement a storage backend
for one of the existing MKs (for example the MongoMK, or the
hi tommaso
the javadoc of org.apache.jackrabbit.mk.api.MicroKernel specifies the
API contract.
org.apache.jackrabbit.mk.test.MicroKernelIT is the integration test
which verifies
whether an implementation obeys the contract.
org.apache.jackrabbit.mk.core.MicroKernelImpl serves as a reference
Thank you all for the very nice pointers!
Regards,
Tommaso
2013/11/6 Stefan Guggisberg stefan.guggisb...@gmail.com
hi tommaso
the javadoc of org.apache.jackrabbit.mk.api.MicroKernel specifies the
API contract.
org.apache.jackrabbit.mk.test.MicroKernelIT is the integration test
which
