A node can be retrieved in two ways: - from his identifier (UUID in JCR 1.0, String in JCR 2.0) - from his path
The identifier approach has the advantage of not being changed if the node is moved, but the node needs to has the mixin mix:referenceable. I think the method renaming has been introduced in JCR 2.0 for not being tied anymore with an UUID but with a String which is back compatible and more flexible (i.e. implementation does not need to respect UUID standard). Regards, -- Sébastien Launay iapilgrim a écrit : > Thanks Launay, > I want to use Session.getNodeByIndentifier. > As I know so far, when we use jcr 1.0, to get a Node, we can use > session.getItem or session.getNodeByUUID. That means an identifier of a node > can be path ( plus name) or its uuid ( if node is referenceable). > So what is the identifier of a node in JR? Is it still a path ( and name)? > What are the new features of identifier in jcr 2.0 over one in jcr 1.0? > I think the new identifier is more natural than the old one and we leave > identifier management to JR. The developer only need to know the identifier > string. Am I right? > I found that SessionImpl (JR 1.4.6) has implemented getNodeByIdentifier but > the javadoc tell it's is used for JR 2.0? Could I use it? And How to use it? > Because I found no test cases for it. > Regard, > van >
