I'm going to rebuild my repository server with 2.0 . From what I understand. I can add what I need incrementally. From what I understand, I'll start the server and add the web dav component
I'll test a local client. Then I'll create a remote client. Does the remote client use jcr2spi + spi2davex components or are these components running with the server? ------Original Message------ From: ChadDavis To: [email protected] ReplyTo: [email protected] Subject: Re: Remote repository Sent: Jan 18, 2010 3:37 PM On Sun, Jan 17, 2010 at 11:49 AM, Christopher M. Logan <[email protected]> wrote: > I've been seeing other messages on the mailing list talking about the > spi2jcr for remote access. Was the spi meant for this usage? Is there > anything available that shows remote access using the spi? > Should WebDAV be used over the spi? > SPI is a necessary part of the WebDAV remoting process, someone correct me if I'm wrong. Here's the WebDAV JCR remoting architecture as I understand it. REPOSITORY SERVER: The repository server side, as I call it, will use a servlet to expose the repository for WebDAV remoting with a servlet, org.apache.jackrabbit.j2ee.JcrRemotingServlet. This servlet can be found in the jackrabbit-webapp maven module's WAR artifact. Run this in a servlet container, etc. CLIENT SIDE: The client application connects with a stack of two components. jcr2spi + spi2davex. Assembling this stack, in 2.0 at least, is handled by using the appropriate factory to create your repository object. Sent via BlackBerry by AT&T
