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
Hi,
On 05.02.2013, at 11:47, Jukka Zitting
jukka.zitt...@gmail.commailto:jukka.zitt...@gmail.com wrote:
Do you have examples of where the new behavior would be troublesome
for existing code (not just new test cases)? The assumption from the
earlier discussion was that such cases should be
Hi,
On Wed, Feb 6, 2013 at 8:04 PM, Marcel Reutegger mreut...@adobe.com wrote:
They are easy to fix but very difficult to detect and diagnose. No exception
is thrown,
just the behavior is unexpected. I think this is quite dangerous, since the
spec is
IMO quite clear about this
hi jukka
i just learned that this discussion wasn't solely about the Tree's
behavior upon move/rename but also affects the JCR Nodes.
as stated in https://issues.apache.org/jira/browse/OAK-606
and https://issues.apache.org/jira/browse/OAK-607
the current behavior is IMO inconsistent between new
Hi,
On Tue, Feb 5, 2013 at 5:20 PM, Angela Schreiber anch...@adobe.com wrote:
as stated in https://issues.apache.org/jira/browse/OAK-606
and https://issues.apache.org/jira/browse/OAK-607
the current behavior is IMO inconsistent between new and existing
nodes and pretty strange from a JCR API
