Hi Alex, sorry for the late reply, I've been out during the past weeks. Actually I'm not sure how to write a unit test for Jackrabbit, beside I am using it through Sling and Jetty, so I cannot provide you the whole code since the architecture I have implemented is quite complex and articulated. Anyway, I will try to write down a small test in the next days.
Thanks, Davide On Thu, Mar 4, 2010 at 11:58 AM, Alexander Klimetschek <[email protected]>wrote: > On Thu, Mar 4, 2010 at 10:52, Davide Maestroni > <[email protected]> wrote: > > Hi Alex, > > > > I did another test removing the node B, so the structure became like > this: > > > > A (mix:versionable, nt:unstructured) > > ^ > > | > > C (mix:versionable, nt:unstructured) > > ^ > > | > > D (nt:file) > > ^ > > | > > E (nt:resource) > > > > When I created a version of A, with the same number of files under C, it > > took only few seconds and the repository size did not increase. > > I'm even more confused now about the expected behavior of VERSION opv. > Can > > you throw some light on it? > > I am not an expert in versioning to say if this is a bug. Could you > provide a short test case (for the case with node B)? Maybe the clue > is in the api calls you make. > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected] >
