Hi, On Mon, Dec 14, 2009 at 4:01 PM, Jukka Zitting <[email protected]> wrote: > On Tue, Oct 20, 2009 at 2:52 PM, Jukka Zitting <[email protected]> > wrote: >> So I'm thinking of putting JCR-RMI on a maintenance track for old 1.x >> releases, and perhaps even dropping the RMI layer entirely from >> Jackrabbit 2.0. > > A better alternative seems to be to upgrade the JCR-RMI layer to JCR > 2.0 and use that in Jackrabbit 2.0. This requires also all clients to > use JCR 2.0, but at least the remoting functionality will still be > there.
I've now (revision 896113) done the groundwork for this upgrade. The JCR-RMI layer now builds and runs with JCR 2.0. Most of the new JCR 2.0 methods simply throw UnsupportedRepositoryOperationExceptions and over 900 TCK test cases fail. However, most of the JCR 1.0 test cases do pass, and the layer seems again roughly usable with Jackrabbit 2.0. Patches that implement at least the most useful new JCR 2.0 methods (look for "TODO: JCRRMI-26" messages in the code) would be very much welcome. BR, Jukka Zitting
