Re: Inconsistent behavior upon moving nodes (was: Re: When moving a Tree, can it die?)

2013-02-07 Thread Dominik Süß
Sorry for jumping in without having the overall picture. Is it really a good idea to use the path as identifier? For Referencable Identifiers (25.1) it is pretty clear that an ID is structureindepenent, so why should a nonreferencable be bound to a path. Since a node can return its path I do not

buildbot failure in ASF Buildbot on oak-trunk

2013-02-07 Thread buildbot
The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/1492 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source Stamp:

Re: buildbot failure in ASF Buildbot on oak-trunk

2013-02-07 Thread Angela Schreiber
sorry for that... will fix... On 2/7/13 11:33 AM, build...@apache.org wrote: The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/1492 Buildbot URL: http://ci.apache.org/

buildbot success in ASF Buildbot on oak-trunk

2013-02-07 Thread buildbot
The Buildbot has detected a restored build on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/1496 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: scheduler Build Source

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Angela Schreiber
in addition we still have an open TODO that the identifier of a non-referenceable node should be as stable as possible which means that it should include the identifier of the parent... in other words: if one of the parent was referenceable the identifier should be somehow combine uuid + relative

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Michael Dürig
On 6.2.13 20:43, Jukka Zitting wrote: The above rationale would imply that in Oak is to make sure that all session refreshes and transient moves should trigger re-evaluation of the the paths of referenceable nodes and those with a referenceable ancestor. Other nodes should keep behaving as

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Angela Schreiber
as far as i remember we never decided to use the path as identifier. we said that we want to keep it as stable as possible... for a referenceable node Node#getIdentifier returns the UUID for a non-referenceable node it should include the parent identifier and a relative path thing. kind regards

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Michael Dürig
On 7.2.13 13:28, Angela Schreiber wrote: as far as i remember we never decided to use the path as identifier. we said that we want to keep it as stable as possible... for a referenceable node Node#getIdentifier returns the UUID for a non-referenceable node it should include the parent

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Jukka Zitting
Hi, On Thu, Feb 7, 2013 at 2:28 PM, Angela Schreiber anch...@adobe.com wrote: as far as i remember we never decided to use the path as identifier. we said that we want to keep it as stable as possible... for a referenceable node Node#getIdentifier returns the UUID for a non-referenceable node

Re: Inconsistent behavior upon moving nodes

2013-02-07 Thread Michael Dürig
On 7.2.13 13:40, Jukka Zitting wrote: Hi, On Thu, Feb 7, 2013 at 2:28 PM, Angela Schreiber anch...@adobe.com wrote: as far as i remember we never decided to use the path as identifier. we said that we want to keep it as stable as possible... for a referenceable node Node#getIdentifier