You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by repository_junkie <al...@gmail.com> on 2009/03/08 20:16:38 UTC
moving from local instance to Jackrabbit server (RMI, WebDAV)
Hi all :)
We are using Jackrabbit along with JCROM (http://code.google.com/p/jcrom/ an
Object Content Mapper) to write a repository service. We started development
using the first deployment model described here:
http://jackrabbit.apache.org/deployment-models.html in the context of an
Application (not a web-application).
Now, we need this repository to be accessible from anywhere on the web
(Therefore clients will definitely be on different VM's). Model 1 no longer
suffices obviously. The clear choice seems to be Model 3: The Repository
Server. (please correct me if I'm wrong). To this end, we've installed the
Jackrabbit Web Application jackrabbit-webapp-1.5.3.war
(http://jackrabbit.apache.org/downloads.html) and deployed it in a tomcat
instance.
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).
My question is, what is the simplest and most common way to install and use
the Jackrabbit server in a production environment? I've been searching for
many days, but unfortunately I have not been able to come up with anything
on nabble either. Could someone please give me a little overview of how I
can go about doing that, or point me to a well-written tutorial or article?
Your help is very much appreciated -- thank you!
Ali
--
View this message in context: http://www.nabble.com/moving-from-local-instance-to-Jackrabbit-server-%28RMI%2C-WebDAV%29-tp22401757p22401757.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: moving from local instance to Jackrabbit server (RMI, WebDAV)
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Mar 9, 2009 at 3:30 PM, repository_junkie <al...@gmail.com> wrote:
> One last question: Does anyone happen to know when apache estimates
> Jackrabbit 1.6 to be released?
My current thinking is to review the status of the trunk next month
after the ApacheCon EU, and to come up with a plan for Jackrabbit 1.6
based on that status. If everything looks good, I would expect to see
a 1.6 release sometime in Q2. Note however that my estimates haven't
been very accurate in the past. :-)
Much of the release schedule depends also on user demand. If there's
notable demand for specific new features, then we can speed up the
release schedule by postponing some other work to 2.0 (or 1.7).
> Also, what are the chances that the SPI package will be fully integrated
> in the 1.6 version?
I think that would be a good idea. See JCR-1877 [1] for more background on this.
[1] https://issues.apache.org/jira/browse/JCR-1877
BR,
Jukka Zitting
Re: moving from local instance to Jackrabbit server (RMI, WebDAV)
Posted by repository_junkie <al...@gmail.com>.
Alex Wrote:
> 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.
One last question: Does anyone happen to know when apache estimates
Jackrabbit 1.6 to be released? Also, what are the chances that the SPI
package will be fully integrated in the 1.6 version?
Thank you!
Ali
--
View this message in context: http://www.nabble.com/moving-from-local-instance-to-Jackrabbit-server-%28RMI%2C-WebDAV%29-tp22401757p22413419.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
Re: moving from local instance to Jackrabbit server (RMI, WebDAV)
Posted by repository_junkie <al...@gmail.com>.
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 :)
Ali
Alexander Klimetschek wrote:
>
> On Sun, Mar 8, 2009 at 8:16 PM, repository_junkie <al...@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.
Re: moving from local instance to Jackrabbit server (RMI, WebDAV)
Posted by Alexander Klimetschek <ak...@day.com>.
On Sun, Mar 8, 2009 at 8:16 PM, repository_junkie <al...@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