jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@day.com>
Subject Re: SPI: setValue vs addProperty
Date Fri, 01 Feb 2008 13:23:41 GMT
Julian Reschke wrote:
> Angela Schreiber wrote:
> Ah, you mean: 
> - addProperty should succeed even though the property already exists, but

in which case it is equivalent to setValue.

> - setValue should continue to fail when the property does not exist yet?

... (rather) doesn't exist any more... because otherwise
you would (hopefully) never get the corresponding jcr-Property.

maybe i'm wrong... but that's how i would define the distiction
between Node.setProperty and Property.setValue assuming your
jcr-api is on client.

but, honestly, i didn't check if jcr2spi behaves according to
that. and i don't remember that the spec explicitly defines
the special situations that might occur in the client


View raw message