Hi, On the other hand, the jcr/jackrabbit-server bundle has a > > DynamicImport-Package: * > > header, which allows it to import just about everything which is > exported elsewhere, dynamically and on-demand. > > This means, you could create a bundle, which exports for example your > LoginModule and the jcr/jackrabbit-server bundle could pick it up. >
Yes it´s true. That´s the way. It gets more complicated with providing a PersistenceManager, because > there is no proper API for that, the respective interfaces and abstract > classes are intermixed with implementation classes. Thus exporting the > required packages is simply not possible. Oops, bad news. And finally: Jackrabbit setup is static. Jackrabbit is not prepared to > implementations going away (or being updated) at runtime. This makes > hooking in PersistenceManagers or LoginModules even more problematic. > Again, we might raise a case in Jackrabbit and try to convince them > about the issues. Do you think jackrabbit team could be sensitive to this issue?. IMHO, this is an important thing to Sling. 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? ;) BR, Juanjo.
