Hi,
On 12/13/06, Joshua Levy <[EMAIL PROTECTED]> wrote:
Jukka Zitting wrote:
> Note that Jackrabbit does not yet implement this solution, so for now
> the only workaround is to either avoid such characters in string
> properties or to use custom import/export mechanisms.
Aha, I see. Thanks, Jukka.
Roughly, is there an expected time frame for such
maintenance draft features to get finalized and implemented?
I would expect Jackrabbit 1.3 to contain this and other JCR 1.0.1
fixes. An early time estimate for a 1.3 release would be sometime by
the end of Q1 next year.
Please file a Jackrabbit bug report about this to better track the
progress on the issue.
BR,
Jukka Zitting