hi julian
that was exactly the reason for not 'hardcoding' the
ValueFactoryImpl as it is the case in jackrabbit.
if you look at the spi2dav project you will find
a slightly modified ValueFactoryImpl, that deals
with exactly this issue.
however i would argue, that it depends on the spi
implementation what kind of ValueFactory it wants
to use. and that was exactly the point, where i
added the ValueFactory to the config together with
the service.
regards
angela
Julian Reschke wrote:
Angela Schreiber schrieb:
...
btw: there is a simple ValueFactory in the jackrabbit-commons
package. you may use this one or provide your own.
BTW:
That ValueFactory unfortunately isn't as generic as I would like: it
enforces Reference properties to use UUID syntax, which of course isn't
always true.
Would it make sense to lift that restriction?
Best regards, Julian