Hi, Good thing. I just checked it out and have a quick look at it. Here is a first impression:
I think, we probably don't need to export everything from this bundle (yet, testing this would be important). Rather we should probably export the most important factory classes: The Server and the Client factories and keep the rest private as implementation details. The factories should take care of getting the class loaders straight. In addition, the bundle contains Jackrabbit-API and hence a Jackrabbit dependency, which is what we wanted to prevent IIRC. The problem is not, that this module is _using_ jackrabbit API but it is _implementing_ jackrabbit API, and this makes it even more problematic, since this generates versioning issues (the imports must be more strict). WDYT ? Regards Felix Jukka Zitting schrieb: > Hi, > > I'd like to start releasing individual JCR Commons components so we > can simplify the Jackrabbit core before the 1.6 release. > > JCR-RMI is the component I've been using for setting up things in JCR > Commons. I think the component is getting close to being released by > itself, so I'd like anyone interested to give > jackrabbit/commons/jcr-rmi/trunk a quick look to check if everything > is OK. Note that (like the earlier versions), the component is a > proper OSGi bundle. > > I'll still be making some build tweaks (enable the Maven GPG plugin, > etc.), but once I'm happy with all the details I plan to cut a > candidate for the JCR-RMI 2.0.0 release. > > BR, > > Jukka Zitting >
