XMLExport change of formats from 9.2 to 9.5

In going from 9.2 to 9.5 the XML Export format has changed. The documnet LiveLink's XML Export and Import Guide does not talk about changes in the XML format between versions, is there a document that talks about the changes?One of the examples follows:When using 9.5 LAPI I notice that in my header I get the following new formats: or instead of <livelink applanguage='USA' appversion='9.2.0' dtdversion='1.2'

Find more posts tagged with

Comments

Jeff_Etrick

After further digging, it seems that in Livelink 9.2, the "scope=sub" attribute returned ONLY the descendants of the requested node, while in 9.5 the same attribute returns the node AND its descendants. Has this been a problem for other developers who rely on the XML to be structured the same way?Is there an XML Schema available for Livelink???

eLink User

Message from Carsten Kulms via eLinkAfaik you find the schema in the subdirectory ./support/xml/xsd of theLES installation.

Jeff_Etrick

When using XMLExport I can specify content={cdata,plain,base64} but what do I need to set to XMLExport to not include the content?

eLink User

Message from Carsten Kulms via eLinkJust do not specifiy the "content" parameter.

Jeff_Etrick

The content does not appear if you omit the "content" parameter in the URL via a browser. However, I am using the LAPI XMLExport call which takes the same set of attributes, and omitting the "content" attribute still results in content being returned. This was not the case in Livelink 9.2, but seems to be the case in 9.5 and 9.7.In 9.5, if you omit the content attribute, the call returns "base64" for non-text and "plain" for textual data.In 9.7, if you omit the content attribute, it returns "base64" for all data, regardless of type.Is there any way to omit content from the XML being exported via the LAPI call?

eLink User

Message from Carsten Kulms via eLinkSorry, I misunderstood the problem.For 9.5.0 SP 1 the behaviour has been corrected with the December 2006patch, cf. the corresponding release notes(https://knowledge.opentext.com/knowledge/llisapi.dll/Readme_for_December_2006_9.5_SP1_Patch_Release.txt?func=doc.fetch&nodeId=9952741&viewType=1):# LAPI XMLExport transform and stylesheet do not work properly.# LAPI XMLExport exports contents of node data regardless of content # parameter specified.# LPO-275 (2058768), LPO-274 (2058769), PAT00122If you use a different LES version and you find that this patch is notavailable for taht version please contact Open Text Customer Support.

Jeff_Etrick

Thanks, Carsten. I do see this problem mentioned in the 9_5_0sp1 patch Readme. However, I have already upgraded to LL 9.7 and I still cannot retrieve the XML without any content. Is there a patch to 9.7 that must be applied, or is there a special option that needs to be passed as the content value? I tried both omitting the content attribute altogether, and setting it to a blank string.

eLink User

Message from Carsten Kulms via eLinkIt seems the issue is not solved in 9.7. I do not know whether a patch is available or scheduled. (I am just a`LAPI user`; neither a LAPI developer nor a member of the support team.)Please contact the Open Text Customer Support.(Include a link to this discussion thread in the request.)