Hi, >So I was thinking of using an explicitly invalid JCR name pattern >For example, the child ordering information in >OAK-169 could go to a ":childOrder"
+1 (I thought that always was idea) >The oak-jcr component could then internally access and >manipulate such properties And/or oak-core (I think we should do as much as possible within oak-core). > excluding the branch where the query index is saved from observation. > Otherwise we'd create zillions of observation events for index updates. That's a good point. I created OAK-181 to track that. Regards, Thomas
