Hans Stoop----------------------LivelinkUp Europe 2002Open Text User ConferenceParis, FranceApril 14-17, 2002Find out how we're helping five million great mindswork together to improve efficiencies and save money.http://www.opentext.com/livelinkup/
-----Original Message-----From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: LAPI DiscussionSent: woensdag 27 maart 2002 21:25To: eLink RecipientSubject: Extending Livelink's XML Capabilities... Extending Livelink's XML Capabilities... Posted by eLink on 03/27/2002 03:25 PM Message from Sean M Alderman <sean.m.alderman@grc.nasa.gov> via eLinkThis topic is partly a feature question and partly a developmentquestion. I've been playing around with a java application (which I'malso in the process of developing) which I want to make use of the XMLExport function in Livelink 9.0... The problem I've run into is thatthe xml export doesn't return enough data about the item I export. Specifically not category/attribute data. I'm looking at writing anoverride (or perhaps a supplement function in oscript) to xmlexport morestuff about an object. Feature-wise, will more object data in livelink be xml accessible in thefuture? Has anyone written any customizations that export more xml datathan what's standard with the existing functionality? If so, would yoube willing to share some of your insights about this?In LAPI, why aren't there any functions documented which can be used tograb xml data from Livelink? Will there be such functionality in futureversions? I currently have to simulate a webclient in order to run thexmlexport function to get an xml file for my java app to work with.-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795Calling a windowed operating system "Windows" is like naming anautomobile "Wheels."