jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From repository_junkie <ali.aje...@gmail.com>
Subject Re: moving from local instance to Jackrabbit server (RMI, WebDAV)
Date Mon, 09 Mar 2009 13:19:17 GMT

Hi Alex, 

Thank you for the prompt response!
Just to confirm and clarify: There is currently no "production-grade"
mechanism for accessing the Jackrabbit server remotely?

I am open to experimenting with both the SPI (although I have tried, but
sadly documentation is quite scarce) and Sling. Does the API that you use
for SPI and Sling differ from the one we are currently using for JCR? I'm
trying to wrap my head around how we can make JCROM work with these
technologies, because we are using JCROM on top of Jackrabbit - meaning that
our own code does not access the JCR layer directly. 

It was easy to do this for the RMI: instead of using a TransientRepository,
we used the URLRemoteRepository, handed it to JCROM, and everything worked.
What will the experience be if we try to use SPI or Sling? 

Thanks again for all your help :) 

Alexander Klimetschek wrote:
> On Sun, Mar 8, 2009 at 8:16 PM, repository_junkie <ali.ajellu@gmail.com>
> wrote:
>> If I understand it correctly, there are currently two ways of interacting
>> with the jackrabbit server: 1. RMI 2. WebDAV. I've been able to integrate
>> the RMI version successfully (by using the URLRemoteRepository), but as
>> the
>> documentation itself admits, the RMI service is PAINFULLY SLOW. I haven't
>> been able to do the same for the WebDAV service. I don't know much about
>> WebDAV, other than it's used for accessing and managing files remotely.
>> Also, I can't find any documentation on how to access the repository
>> through
>> code on the WebDAV protocol (Like the RMI).
> There is some work going on in the Jackrabbit sandbox with an improved
> remoting using SPI over Webdav with Json as exchange format [1].
> Please join the dev@ list for the ongoing development. I estimate this
> might also be part of the 1.6 release of Jackrabbit.
> Another option is to look at Apache Sling, a webapplication framework
> on top of JCR, that provides the full JCR API in a RESTful way. By
> using its REST interfaces (or easily writing your own!) in a
> document-granular way, you can also tune your performance for a remote
> JCR application.
> [1] https://issues.apache.org/jira/browse/JCR-1958
> [2] http://incubator.apache.org/sling
> Regards,
> Alex
> -- 
> Alexander Klimetschek
> alexander.klimetschek@day.com

View this message in context: http://www.nabble.com/moving-from-local-instance-to-Jackrabbit-server-%28RMI%2C-WebDAV%29-tp22401757p22412946.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

View raw message