Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44F22757.4090001@eyestreet.com>
Date: Sun, 27 Aug 2006 19:14:31 -0400
From: Harry Moore <harry.moore@eyestreet.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: users@jackrabbit.apache.org
Subject: Re: Standard remote access
References: <44F1B47D.5080208@eyestreet.com>
 <510143ac0608271413w10bceae9l1a089168b1ab0c46@mail.gmail.com>
In-Reply-To: <510143ac0608271413w10bceae9l1a089168b1ab0c46@mail.gmail.com>
Content-Type: multipart/mixed;
 boundary="------------020006010906040508060100"

--------------020006010906040508060100
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Does that mean it is up to me to setup the RMI adapter on each vendors' 
system or do vendors generally provide this?

Thanks,
Harry

Jukka Zitting wrote:
> Hi,
>
> On 8/27/06, Harry Moore <harry.moore@eyestreet.com> wrote:
>> I'm working on an application that will copy a workspace either in whole
>> or in part between JCR compliant repositories by various vendors. The
>> repositories are likely to be on different servers. I'm wondering if
>> anyone has researched the various vendors (Day, Alfresco, Magnolia, etc)
>> on whether or not there is a common method of remote access.
>
> The JCR-RMI adapter works on top of the JCR API, i.e. it has no
> dependencies to the Jackrabbit core. Thus it should work without
> problems with any compliant repository.
>
> BR,
>
> Jukka Zitting
>

-- 
Harry Moore
Eye Street Software
Office: 301-813-3013
Fax: 301-813-3413


--------------020006010906040508060100--