Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@manifoldcf.apache.org
Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates
 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPfsL=7Rvc-D+VcDD2vjnukmri=8Gqcm0-UPRzf4SXCNumaKSw@mail.gmail.com>
References: 
 <CAPfsL=7Rvc-D+VcDD2vjnukmri=8Gqcm0-UPRzf4SXCNumaKSw@mail.gmail.com>
Date: Mon, 8 Dec 2014 06:38:42 -0500
Message-ID: 
 <CALUFAGBDWyWMOpiFOQ=JVd1fEyp0MUbi+XFn+urN1fEyG3HWSw@mail.gmail.com>
Subject: Re: Support for OpenText Livelink Webservice API
From: Karl Wright <daddywri@gmail.com>
To: dev <dev@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1dcde59f4790509b2de3d

--001a11c1dcde59f4790509b2de3d
Content-Type: text/plain; charset=UTF-8

Hi Odilo,

I answered this question not long ago on the same list.
In order for us to develop a new Livelink connector that does not rely on
LAPI, the following things would be necessary:

(1) A user who is willing to work with us over an extended period of time
to develop such a connector
(2) If it's SOAP, we'd also need the WSDLs for the web service(s) that are
meant to replace LAPI functions
(3) It's possible, depending on how much use of XSDs that such an API makes
use of, that we'd be unable to fully support the current functionality of
the Livelink connector in the new world -- but we won't know that until at
least (2) takes place

Thanks,
Karl


On Mon, Dec 8, 2014 at 5:14 AM, Odilo Oehmichen <odilo.oehmichen@gmail.com>
wrote:

> hi,
>
> currently manifolds supports the LAPI for querying an OpenText Livelink
> repository. - This api is marked deprecated (see [0]).
>
> Are there any plans to support the new CS SOAP Webservice API in
> manifoldCF?
>
> cheers,
> odilo
>
> [0] https://developer.opentext.com/awd/forums/questions/1130441#r1130448
>

--001a11c1dcde59f4790509b2de3d--