jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@day.com>
Subject Re: session.move issues
Date Tue, 16 Mar 2010 20:18:55 GMT
hi

i fixed 2 move/copy issues during the last couple of weeks:
JCR-2472, JCR-2565

can you please check if any of them is identical to your problem?

btw... it would be more helpful if you would just provide a
simple test-case illustrating the problem instead of a
long description...

regards
angela

ChadDavis wrote:
> JCR-2572
> 
> On Tue, Mar 16, 2010 at 11:51 AM, ChadDavis <chadmichaeldavis@gmail.com> wrote:
>> I've narrowed down the scope of this issue.  It seems that this occurs
>> only when the nodes are mix:versionable.  I'll enter the full details
>> in Jira.
>>
>> On Tue, Mar 16, 2010 at 7:29 AM, Stefan Guggisberg
>> <stefan.guggisberg@gmail.com> wrote:
>>> hi chad
>>>
>>> On Mon, Mar 15, 2010 at 10:44 PM, ChadDavis <chadmichaeldavis@gmail.com>
wrote:
>>>> I'm getting an exception on session.save() after session.move().
>>>>
>>>> Here's some pseudo code just to verify that my approach is correct.
>>>>
>>>> oldNode = session.getNode("/a/b");
>>>>
>>>> session.move( oldNode.getPath(), "/a/c" );
>>>>
>>>> newNode = session.getNode( "/a/c" );
>>>>
>>>> session.save()
>>>>
>>>>
>>>> The save throws javax.jcr.PathNotFoundException on the path "/a/b",
>>>> which is the old node.
>>>>
>>>> Should this work?
>>>>
>>> definitely. please create a jira issue and if possible provide a
>>> simple test case
>>> which demonstrates the issue. please also provide detailed information
>>> about your environment (versions, deployment model, remoting stack etc).
>>>
>>> thanks
>>> stefan
>>>
> 


Mime
View raw message