LAPI - Will It Ever Be Changed

For the last 2 years, I have been forced to code using the LAPI for Java. Although promised changes in v9 (perhaps to OO code and reported Exceptions), all we got was an additional load of poorly-documented, bass-ackwards classes that use mystic LLValues as the all-encompassing Data Object.Tha LAPI Documentation states:"Many of the functions in the other APIs use value objects as input and output parameters. This provides several advantages...This should read: "In order to prevent anyone from understanding what the LAPI is doing (hence limiting development beyond what we will sell you), and since Java utterly lacks sufficient Objects to represent the extremely special Livelink Data, we have developed the LLValue Object.Additionally, since we are too cheap to hire anyone to code the LAPI who might assist in making the LAPI understandable to a Java developer, we essentially guarantee a continuing revenue stream from development support training.We back our commitment to strangle development up by removing all sample code from the shipped documentation."Come on, Open Text, why not accept the criticisms of the LAPI and provide a true OO/Java API so we could actually do some work.I would code a good Java LAPI for you for money.I can't wait to see how you do the J2EE version of Livelink (by having the controller servlet do HTTP calls to the same old Livelink system, I bet!Any other comments!Jon Kofal

Find more posts tagged with

Comments

sıɹɥɔ

Message from Chris Webster <cwebster@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Declan,

Yes, it's true that LAPI is not oriented towards Java. I think part of the reason for this is that LAPI was in fact designed to accommodate multiple languages, and as such doesn't follow the conventions a Java developer might expect.

Having said that I highly recommend that you investigate SLAPI or EasyLAPI. These opensource libraries were written by developers who wanted a Java-style interface to LAPI. Using them you'll find much less need to deal with infamous LLValue's. (There are even javadocs!) These libraries are not official Open Text products, and hence unsupported, but at a minimum are useful demonstrations of how to make LAPI more Java friendly.

You can find EasyLAPI ans SLAPI by visiting the Livelink SDK DevZone at: https://knowledge.opentext.com/devzone

and following the link to LAPI Tools & Apps.

-chris

From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, September 24, 2008 7:34 AM
To: eLink Recipient
Subject: Interesting to read all the same problems that I am experiencing...

Interesting to read all the same problems that I am experiencing...		Posted by declan.wilson@almacgroup.com (Wilson, Declan ) on 09/24/2008 08:28 AM
In reply to: RE "Not received a meaningful number of samples"		Posted by testcsstaff on 07/26/2006 09:46 AM

Interesting to read all the same problems that I am experiencing...
It seems that the LAPI code is a direct mapping from the propriertary Oscript version of these methods. In no way would I describe it as a Java API.
Howinever, 6/7 years later, from the original post ... can I ask have OpenText revised the LAPI code, to something more standard?
Is there a community area up and running yet?
Is there a shared examples area?

Declan_Wilson

Many thanks Chris ... this should provide a good start for the development efforts we need to perform.cheersDeclan