On Mon, May 6, 2013 at 11:01 PM, Jay McHugh jaydmch...@gmail.com wrote:
...So, to try to figure out where my data really is - what property (or
properties) should I look for in the configuration XML files?...
Here's two unixish command-line tricks that can also help finding that out:
a) Use
hi lars,
i met jukka last week and he explained me how this works, and actually
when you know where to look, it kind of is written in the spec:
* cloned nodes share the version history, so checkins in either
workspace go into the same history.
* when updating, jackrabbit at least is using this
hi lars,
jukka also helped on this one:
this is basically specified in
http://www.day.com/specs/jcr/2.0/3_Repository_Model.html#3.13.9%20Versionable%20State
* copy: always copy the children until hit ignore
* version: same as copy except when a child is versionable it is skipped
checkins are
Thank you Jukka and Bertrand.
That helped a lot!
Jay
On Tue, May 7, 2013 at 6:41 AM, Bertrand Delacretaz
bdelacre...@apache.orgwrote:
On Mon, May 6, 2013 at 11:01 PM, Jay McHugh jaydmch...@gmail.com wrote:
...So, to try to figure out where my data really is - what property (or
Hi Ferry,
looks like, you're writing on several nodes.
You should concentrate all write access on one clusternode. I've
experienced best write performance using jcr single write multiple read
in clustered env. The more nodes with write access trying to aquire a
revision in journal, the more
Thank you Claus!
Jay
On Tue, May 7, 2013 at 12:27 AM, KÖLL Claus c.ko...@tirol.gv.at wrote:
Hi Jay,
The Janitor is described here ...
http://wiki.apache.org/jackrabbit/Clustering#Removing_Old_Revisions
You can enabled the janitor without any headaches .. you will have no
impacts ..
As
