Hi, I'm looking to implement something resembling a 'materialised view' over content; essentially a special node which acquires or loses references to checked in nodes depending upon whether they match a given query. Since I need the query to run after property indexing takes place, I've been looking to plug an Observer which also has access to the NodeStore for writing the results (ala Lucene's async indexer).
I believe the best way to have my Observer access the NodeStore is via @Reference injection from the OSGi container. I have no plans to use OSGi however so I've been looking at using PojoSR taking inspiration from the tests here: https://github.com/apache/jackrabbit-oak/tree/trunk/oak-pojosr/src/test/groovy/org/apache/jackrabbit/oak/run/osgi . Unfortunately pursuing this line has been a massive time sink where all roads lead to a timed out test due to an incorrectly configured container. I could go into detail about this journey if it would help but given the about of work I had to do just to get this far, I feel like my approach is wrong. Also the whole PojoSr project feels unmaintained. So - how would you recommend I attack this problem? How do I spin up a test that allows me to inject a NodeStore into my Observer and then perform session operations? Any help very appreciated! Regards - Paul
