jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Hugonnet <ehsavoi...@gmail.com>
Subject Re: Remoting and future of JCR-RMI
Date Wed, 23 Dec 2009 22:37:05 GMT
I was porting an eXo JCR shell tool (http://code.google.com/p/crsh/)
to Jackrabbit and this incompatibility as driven me back to 1.6.
Jukka you mentioned  another post : <quote>
At Day we've been increasingly using the spi2dav layer, and except for
being a bit more complicated to set up (see my other post on how to
address that issue) it's already quite usable as a replacement for
JCR-RMI.</quote> I assume it is the JCR-2360 issue, am i right ?

If webdav is the way to get for remote access, could you please give
us some documentation on how to configure the client and server for
this communication ?


On Tue, Dec 15, 2009 at 4:21 PM, Ard Schrijvers
<a.schrijvers@onehippo.com> wrote:
> Hello Jukka,
> On Tue, Oct 20, 2009 at 2:52 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>> With enough work we could solve both of the above issues to make
>> JCR-RMI work with all combinations of JCR 1.0 and 2.0 clients and
>> servers. However I'm not convinced that it makes sense to spend all
>> that effort when we now have the WebDAV-based remoting layer that's
>> already pretty feature-rich.
> I haven't worked with WebDAV since the move of Slide to Jackrabbit,
> but I remember there was no support for DASL before. How do other
> people query a remote repository over WebDAV?
> I also used to think that most developers and users that were
> accessing a standalone repository would do so by connecting over RMI
> (or does it happen to be webdav?)...we at Hippo do so during
> development at least, and use embedded repositories in a production
> mode
> Regards Ard
>> 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.
>> WDYT?
>> BR,
>> Jukka Zitting

View raw message