Hi,

the JCR Resource implementation currently allows to adapt it to a url which
internally embeds several jackrabbit classes. The returned object keeps
hold of the current session and therefore is a potential memory leak and
can't be used once the session is closed.
So far I've not seen any real use case for this and especially as other
resource implementations do not provide it, what about deprecating this
now, logging a big message when used (once) and then we can remove it in
one of the next versions?

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Reply via email to