Hi,
On 2/28/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
according to the spec Item.getPath() is different in this respect. that is, you
can get the path of an item even though an ancestor of an item is not 'visible'
to you. I put visible in quotes because at least the name of the ancestor
On 3/2/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Hi,
On 2/28/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
according to the spec Item.getPath() is different in this respect. that is,
you
can get the path of an item even though an ancestor of an item is not
'visible'
to you. I put visible
Hi,
On 3/2/07, Stefan Guggisberg [EMAIL PROTECTED] wrote:
On 3/2/07, Jukka Zitting [EMAIL PROTECTED] wrote:
The only thing being protected is that the client will not have a
reference to a parent or ancestor node. I could always construct a
custom Node instance myself that would act just
Hi,
On 2/28/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
please note that getParent() may also throw an access denied exception, in case
the session does not have sufficient access rights for an ancestor. however
getDepth() should still succeed in that case.
Hmm, good point. I think it's a
