Which XML utility should one use?

Hello:I'd like to know which XML utilities one should rather use:1. Built-in Package DOM and SAX parsers - Advantage: Standards-based - Disadvantage: Cryptic to use through livelink, e.g. how do I get the created XML document back into a string?2. $LLIAPI.XMLWriter.* - Advantage: Simple to understand and use - Disadvantage: Is it officially supported, and will it be made compatible with different character sets (e.g. UTF-8)?The first one doesn't seem to be in use at all. The second more than the first in Open Text provided modules....I'd settle for the $LLIAPI XML utilities, but will these be supported in future releases.One could just string-create the XML, but I think this will be increasingly clumsy for support in different character sets?Anyone from Open Text care to provide an answer?Thanks,Rolf.

Find more posts tagged with

Comments

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

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

Hi Rolf,

I think you make a strange comparison.

$LLIAPI.XMLWriter is for creating XML files. The DOM and Sax parser is for parsing existing XML files.

The Sax parser is used for xmlImport.

In Livelink 9.5 $LLIAPI.XMLWriter is replaced with $XML.XMLWriter. The functions seems to be the same.

The XML output character-set in Livelink 9.5 will be either ISO-8859-1 or UTF-8, depending on the internal Livelink format. If you want to use a specified character-set, you need to do the character conversion yourself.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 20 december 2004 18:30
To: eLink Recipient
Subject: Which XML utility should one use?

Which XML utility should one use? Posted by SBSUser06 (Poser, Rolf) on 12/20/2004 12:29 PM

Hello:

I'd like to know which XML utilities one should rather use:

1. Built-in Package DOM and SAX parsers
- Advantage: Standards-based
- Disadvantage: Cryptic to use through livelink, e.g. how do I get the created XML document back into a string?
2. $LLIAPI.XMLWriter.*
- Advantage: Simple to understand and use
- Disadvantage: Is it officially supported, and will it be made compatible with different character sets (e.g. UTF-8)?

The first one doesn't seem to be in use at all. The second more than the first in Open Text provided modules....

I'd settle for the $LLIAPI XML utilities, but will these be supported in future releases.

One could just string-create the XML, but I think this will be increasingly clumsy for support in different character sets?

Anyone from Open Text care to provide an answer?

Thanks,
Rolf.

Rolf_Poser_(sbsuser06_-_(deleted))

Hans:I don't think it's strange - I've used DOM parsers elsewhere to create an XML document from scratch.... Actually, I enjoy jdom the most, so maybe using the Java module will be the ultimate answer.....Thanks for the info on $XML - I'm not too keen to use any format other than standard ones, but I'd rather let the utilities worry about that. One of the things one may want to do (sometimes - perhaps more of a theoretical case) would be to choose the character set when generating the document, and let the XML utility worry about generating it in the right format..... A nice example would be to use UTF-8 on Livelink, but to allow for integration with legacy systems that only talk US-ASCII or ISO-8859-1, which are both subsets of UTF-8....Anyway, as I say - it's theoretical for me at the moment... The main thing is that there is continuity, and a slight modification will port my custom module to 9.5 (and hopefully beyond)...Regards,Rolf.

Magnus_S_(novnoruser_-_(deleted))

Will $LLIAPI.XMLWriter still be useable in 9.5 ....Still develop with 9.2Magnus

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

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

No. There is no $LLIAPI.XMLWriter in 9.5. All XML stuff moved from $LLIAPI to $XML.

In 9.2 you can already make use of $XML.XMLWriter.

The new XML framework is already in place in Livelink 9.2.

In 9.2 XML import and XML export make use of the 'old' framework. The project templates make use of the 'new' framework.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: woensdag 22 december 2004 9:33
To: eLink Recipient
Subject: 9.5 and $LLIAPI.XMLWriter

9.5 and $LLIAPI.XMLWriter Posted by NOVNORUser on 12/22/2004 03:28 AM
In reply to: RE Which XML utility should one use? Posted by hstoop (Stoop, Hans) on 12/20/2004 03:27 PM

Will $LLIAPI.XMLWriter still be useable in 9.5 ....

Still develop with 9.2
Magnus

Rolf_Poser_(sbsuser06_-_(deleted))

Hans:On that note - I've found project import/export very useful to move some content (e.g. workflows and forms) between instances - quite handy.I don't seem to be able to stick a community inside of a project and then export it. I guess it wasn't really built for that purpose, but it'd be nice :-)Regards,Rolf.

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

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

In 9.5 that should also work correctly with the standard XML import/export.

If you are not able to create it inside a project, you can try to change the parentID in the DTree table to point to the project WS ID.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: woensdag 22 december 2004 11:21
To: eLink Recipient
Subject: On that note... exporting communtities

On that note... exporting communtities Posted by SBSUser06 (Poser, Rolf) on 12/22/2004 05:15 AM
In reply to: RE 9.5 and $LLIAPI.XMLWriter Posted by hstoop (Stoop, Hans) on 12/22/2004 04:03 AM

Hans:

On that note - I've found project import/export very useful to move some content (e.g. workflows and forms) between instances - quite handy.

I don't seem to be able to stick a community inside of a project and then export it.

I guess it wasn't really built for that purpose, but it'd be nice :-)

Regards,
Rolf.

Rolf_Poser_(sbsuser06_-_(deleted))

Alas - CoP for 9.5.0 is only due next year Apr/May, so I'll follow your second line of advice for now...Thanks for the info,Rolf.

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

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

Let us know if it worked.

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: woensdag 22 december 2004 11:57
To: eLink Recipient
Subject: Great - thanks I'll try that...

Great - thanks I'll try that... Posted by SBSUser06 (Poser, Rolf) on 12/22/2004 05:55 AM
In reply to: RE On that note... exporting communtities Posted by hstoop (Stoop, Hans) on 12/22/2004 05:41 AM

Alas - CoP for 9.5.0 is only due next year Apr/May, so I'll follow your second line of advice for now...

Thanks for the info,
Rolf.