atom feed21 messages in org.apache.jackrabbit.oak-devRe: Internal content in Oak
FromSent OnAttachments
Jukka ZittingJul 12, 2012 4:11 am 
Julian ReschkeJul 12, 2012 4:18 am 
Michael DürigJul 12, 2012 4:22 am 
Thomas MuellerJul 12, 2012 4:44 am 
Jukka ZittingJul 12, 2012 5:15 am 
Angela SchreiberJul 17, 2012 4:01 am 
Jukka ZittingJul 18, 2012 7:16 am 
Thomas MuellerJul 19, 2012 12:21 am 
Stefan GuggisbergJul 19, 2012 1:18 am 
Jukka ZittingJul 19, 2012 1:37 am 
Angela SchreiberJul 19, 2012 1:54 am 
Jukka ZittingJul 19, 2012 1:57 am 
Jukka ZittingJul 19, 2012 2:09 am 
Thomas MuellerJul 19, 2012 2:25 am 
Stefan GuggisbergJul 19, 2012 2:26 am 
Thomas MuellerJul 19, 2012 2:29 am 
Jukka ZittingJul 19, 2012 2:36 am 
Angela SchreiberJul 19, 2012 2:59 am 
Jukka ZittingJul 19, 2012 3:26 am 
Alexander KlimetschekJul 19, 2012 11:58 am 
Jukka ZittingJul 19, 2012 2:09 pm 
Subject:Re: Internal content in Oak
From:Thomas Mueller (muel@adobe.com)
Date:Jul 12, 2012 4:44:20 am
List:org.apache.jackrabbit.oak-dev

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