Hi Carsten, On Jan 25, 2010, at 9:02 AM, Carsten Ziegeler wrote: > I think we briefly discussed this topic some time ago: the Jackrabbit > 1.x versions provide a repository classloader which is not available > anymore in 2.0.
Can't find any related thread. Any pointer ? > In Sling we provide a complete scripting framework based on top of the > repository and we're using the Jackrabbit classloader code and extended it. > > As Jackrabbit is not using the code anymore, but Sling is, I think it > makes perfectly sense to move/copy the code to Sling. As far as I can tell, it's in the "commons" folder [1] - it's an optional component that's indeed not bundled with Jackrabbit. TBH, I haven't looked at it very closely, but I'd it is/could/should be independent of Jackrabbit, i.e rely on the JCR API alone. > So I would like to copy the classloader code into the Sling repo in the > next days and modifiy it to suit Sling's needs a little bit more. This > has no impact on Jackrabbit as 2.0 does not contain the code at all and > it still remains in the 1.x branch. Again - afaict, it's not in either branch, it's a separate component. > Basically this is more a FYI as no legal steps etc are involved :) But > before doing this I want to be sure that there are zero objections. I'm only answering because I'd like to have a close look at it one of these days, and hopefully use/improve it, too. If it stays repository- and application-neutral. If it becomes tied to Sling, not so much. What kind of changes/improvements are you looking into ? Cheers, -g [1] https://svn.apache.org/repos/asf/jackrabbit/commons/classloader/trunk/
