jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rosselet <ati.rosse...@gmail.com>
Subject baseline/configuration sub-tree as frozen-node rep:version references?
Date Wed, 19 Oct 2011 20:32:29 GMT
>From looking at the code, and trying to figure out how the configuration node
works,  am I correct that at least currently the configuration node doesn't
actually store a subtree consisting of references to the node versions at
the time of the config being commited, but rather a LIST of these frozennode
references?

in VersionManagerConfigImpl.java  
commit does this:
                    Set<NodeId> baseVersions = collectBaseVersions(state);
                    InternalValue[] vs = new
InternalValue[baseVersions.size()];
                    int i=0;
                    for (NodeId id: baseVersions) {
                        vs[i++] = InternalValue.create(id);
                    }
                    state.setPropertyValues(NameConstants.REP_VERSIONS,
PropertyType.REFERENCE, vs);
which appears to support what I have seen: multivalued "rep:versions"
property with UUID references to the correct frozen nodes for that point in
time.  

Is there currently any way to get this as a "sub-tree", or can I at least
assume that the sub-tree was walked breadth-first? (are parents ensured to
always appear in this multivalue list before children?)

or.. am I missing something completely????
thanx
Ati

--
View this message in context: http://jackrabbit.510166.n4.nabble.com/baseline-configuration-sub-tree-as-frozen-node-rep-version-references-tp3920033p3920033.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

Mime
View raw message