best practice : storing custom properties somewhere eles for versioned resources ?

[Lixin Chu <li...@gmail.com>]

Hi,
I am stuck with managing custom properties for versions resources. 

I am not sure if my understanding is correct: when we change the value
of any custom property, a new revision of the resource will always be
created.

Since I do not want to have a new version created when I modify the
value, does it mean that the only way is to store the custom property
somewhere else ?

Is it a common practice to use a dedicated store for keeping the
custom properties for versioned resources ?

thank you very much !
li xin

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org