Re: Problem with Move Copy operations.

2009-12-31 Thread Alexander Klimetschek
On Tue, Dec 29, 2009 at 12:02, Ian Boston wrote: > In my repository.xml I have > > class="org.apache.jackrabbit.core.security.DefaultAccessManager"> AFAIK the DefaultAccessManager in Jackrabbit >= 1.5 does not use the ZombieHM at all, so JCR-2321 can't be the reason. I guess this needs debuggin

Re: Problem with Move Copy operations.

2009-12-29 Thread Ian Boston
Yes I can confirm that using the DefaultAccessManager in Sling trunk without any other modifications or code results in the same problem. The question that remains is why? Ian On 29 Dec 2009, at 11:02, Ian Boston wrote: > In my repository.xml I have > > class="org.apache.jackrabbit.core.sec

Re: Problem with Move Copy operations.

2009-12-29 Thread Ian Boston
In my repository.xml I have if I change it to the problem goes away, I am just checking that I can reproduce the problem with unmodified Sling. If I can this is a bit odd since IIRC the PluggableDefaultAccessManager simply delegates to the DefaultAccessManager and has nothing to do with

Re: Problem with Move Copy operations.

2009-12-29 Thread Ian Boston
Alex, That looks possible. It may well have been triggered by the custom AccessManager which may look at item hierarchy in the wrong way. I have narrowed it down to the either the Login Module or the AccessManager. Thanks, Ian On 27 Dec 2009, at 23:45, Alexander Klimetschek wrote: > The problem

Re: Problem with Move Copy operations.

2009-12-27 Thread Alexander Klimetschek
The problem sounds a bit like https://issues.apache.org/jira/browse/JCR-2321 but I am not sure if it really is the same issue, as JCR-2321 depended on the specific implementation of an AccessManager. Regards, Alex On Wed, Dec 23, 2009 at 17:27, Ian Boston wrote: > To confirm. > In my local bundl

Re: Problem with Move Copy operations.

2009-12-23 Thread Ian Boston
To confirm. In my local bundling of Sling, which fails. New Node ID is Old Node is5bc87894-135e-4363-83ce-d5548e727104 New Node is 095b58ec-297f-41d1-867e-0042bf132769 Session node is 5bc87894-135e-4363-83ce-d5548e727104 Same as old node (which it should not be) And from the Sling st

Problem with Move Copy operations.

2009-12-23 Thread Ian Boston
I have a problem that I cant reproduce in Sling, but can reproduce in my local packaging of the same Sling components, and was wondering if anyone had some insights. The steps are create 2 nodes /a1 /a2 Then copy /a1 onto /a2 with overwrite = true using curl -F:operation=copy -F:dest=/a2 -F:rep