Hi, On Thu, Jan 14, 2010 at 11:38 PM, Christopher M. Logan <[email protected]> wrote: > In jackrabbit 1.6 and with moving to 2.0 in mind, what is the recommended > approach to connecting to a remote repository that will preserve full > functionality?
Jackrabbit 2.0 will have two remoting mechanisms, RMI and WebDAV. From a project roadmap perspective the WebDAV remoting is the preferred alternative with the RMI layer kept mostly for backwards compatibility and functional completeness. The RMI layer was a bit troublesome to port to 2.0 but it now works. The upgraded RMI layer is not yet available in the current 2.0 betas, but will be included in the final Jackrabbit 2.0 release. The RMI layer in Jackrabbit 2.0 will cover pretty much all of the JCR 1.0 API, but not many of the JCR 2.0 extensions. The WebDAV remoting layer has a better internal design than the RMI layer and can thus support notably improved performance for many operations. WebDAV remoting isn't as thoroughly tested as the RMI layer and may lack some functionality, but I expect it to improve quickly during the 2.x release cycle. Both mechanisms implement the same JCR API, so it will not be too troublesome to switch from implementation to another later on if needed. BR, Jukka Zitting
