Hi, On Fri, Dec 11, 2009 at 1:47 PM, malligarjunan <[email protected]> wrote: > We cannot change the jackrabbit version now, because we need to test our > application once again and we use it extensively. Please let us know the > code changes which are applicable to this issue.
The relevant bug fix seems to be JCR-1728 [1], fixed in jackrabbit-core 1.4.6. Good luck backporting the fix to Jackrabbit 1.2.x. As Alex mentioned, upgrading to a more recent version is probably much less painful and definitely the recommended approach. [1] https://issues.apache.org/jira/browse/JCR-1728 BR, Jukka Zitting
