On 2013-02-04 19:30, Jan Haderka wrote:
Another bit of info on this issue - if I call session.save() prior trying to 
get the child nodes, I end up with:


javax.jcr.InvalidItemStateException: Unable to update a stale item: item.save()
        at 
org.apache.jackrabbit.core.ItemSaveOperation.perform(ItemSaveOperation.java:262)
        at 
org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
        at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
        at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:329)
….
Caused by: org.apache.jackrabbit.core.state.StaleItemStateException: 
b09228e5-ecca-45e0-9cb4-660337e846ed has been modified externally

So yeah, cause is clear, there was another session that modified the item in 
the mean time. However it doesn't seem right to me that getNodes() call ends up 
with NPE. Do you agree that this is a bug?

Cheers,
Jan
...

It sure sounds like a bug. Maybe you can write a JUnit test case and open a ticket?

Best regards, Julian

Reply via email to