Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Sascha Homeier <shomeier@meyle-mueller.de>
To: =?iso-8859-1?Q?Florian_M=FCller?= <fmui@apache.org>
CC: "dev@chemistry.apache.org" <dev@chemistry.apache.org>
Subject: Re: JCR Bridge
Thread-Topic: JCR Bridge
Thread-Index: AQHP4wIHeFSAnryf+EGpzsDFuM0n0ZwmQfUAgAAt0YI=
Date: Wed, 8 Oct 2014 17:11:27 +0000
Message-ID: <948015F4-78C7-4903-8B50-72217DD4763E@meyle-mueller.de>
References: 
 <3E78A6FF-E8B7-40CC-84F4-39CF3AA150EC@meyle-mueller.de>,<406693c7d878ee986c3dccef2d902647@jpberlin.de>
In-Reply-To: <406693c7d878ee986c3dccef2d902647@jpberlin.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Ok, thx for quick response Florian.

Cheers
Von meinem iPad gesendet

> Am 08.10.2014 um 18:27 schrieb Florian M=FCller <fmui@apache.org>:
>=20
> Hi Sascha,
>=20
> Re 1.) There is nothing like this in OpenCMIS.
>=20
> Re 2.) No, there is no maintainer for the JCR implementation at moment.
> As long as nobody is looking after it, the JCR bridge will not be part of=
 OpenCMIS releases.
>=20
>=20
> - Florian
>=20
>=20
>> Hello together,
>> we have a requirement to connect the Adobe Experience Manager (AEM)
>> with our CMIS server.
>> So the assets and metadata from our CMIS server should be accessed by th=
e AEM.
>> Afaik the AEM or its CRX from Day uses Sling with Jackrabbit and
>> thereby of course JCR.
>> Due to the OpenCMIS JCR Bridge I have two questions:
>> 1.)
>> On the Chemistry Webpage I read that the bridge provides access to JCR
>> repositories from CMIS clients. In fact we need it the other way
>> round: Our CMIS repositories should be visible as JC repositories. Is
>> this at some extent possible with the OpenCMIS Bridge?
>> 2.)
>> Is the bridge still in development?
>> If I remember correctly the original maintainer had not enough time to
>> further manage the component.
>> Did you find a successor?
>> tia
>> Cheers
>> Sascha