Usually this list is justy for people asking questions, so for a change of pace I would like to show how I've been using Jackrabbit/Oak and the kind of thing it has enabled me to do.
Escaping the Tyranny of the Domain https://www.youtube.com/watch?v=uwZj4XF6zic Databases encouraged us to tightly couple our applications to fixed and inflexible data structures. Changes to the data structures could only be made by developers. With the advent of OO languages the data structure was even more closely bound up, with Hibernate like persistence systems making this kind of relationship dangeriously easy. JackRabbit enabled me to go to break this dependency and develop applications that could dynamically define their data structures, and where adding a field was no longer a mission. The ability to register listeners also enabled me to develop automation systems that listen for these events to trigger dynemically defined business rules; rules which are themselves also stored in Jackrabbit. Introduction to Gravity Workflow Automation https://www.youtube.com/watch?v=vUxKeaMjDo0 I originally developed Gravity using Jackrabbit 2.X, but over the last six months migrated to Oak. The transition has not been without it's pain, Gravity is GPL. I am still usinf OCM, which is a Object to JCR mapper a little like Hibernate, although I have made several modifications to my version of OCM to support some use cases I had. So in summary, thanks to the Jackrabbit/Oak devs! This has fundamentally changed how I look at data.
