I've created a ticket for this work: CONNECTORS-1117
Please let us know if you are willing to work with us to develop this connector. Thanks, Karl On Mon, Dec 8, 2014 at 6:41 AM, Karl Wright <[email protected]> wrote: > I should also add that when an equivalent REST api is available, it's > generally far better to write a connector against that, since SOAP is very > verbose, and since sometimes users are reluctant to give us WSDLs that they > think may be proprietary. (We've gotten rulings from Apache Legal that > that is not the case, because WSDLs are interface specifications which > cannot be copyrighted, but your license agreement may cover them.) > > Karl > > > On Mon, Dec 8, 2014 at 6:38 AM, Karl Wright <[email protected]> wrote: > >> 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 < >> [email protected]> 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 >>> >> >> >
