Hi, Agreed. I think if we can present a good use case for the requirement > (which IMHO is a good requirement in itself) the Jackrabbit team would > be more sensitive to the issue. > > Until now, they have not been that much sensitive to this because they > are more concerned with support for the upcoming JCR 2.0 (JSR-283) > standard. >
Understand, the first is first. > > > > Alternatively, you may create your own jackrabbit-server bundle > >> including your special PersistenceManager (or whatever it is). But I > >> agree, this is not the best of all solutions. > > > > > > I know, but sure you hate duplicated code, aren´t you? ;) > > I do, of course ;-) > > But you could create a bundle, which depends on Sling's > jcr/jackrabbit-server bundle but extends it. When building the final > bundle, the jcr/jackrabbit-server bundle stuff would just be included in > your own bundle, for example by means of the <Embed-Dependency> element > of the bundle plugin or by using svn:externals (though this would be > kind of a last ressort IMHO). > Yep, I had already thought about this solution. It could be works. Anyway, I´m still thinking about an eventual jackrabbit-server improvement. Are yoy agree?. BR, Juanjo.
