Comments on: Step-by-step DXL debugging

By: Martin Vereecken

Martin Vereecken — Wed, 16 Jan 2008 19:44:29 +0000

I encountered some problems too, and for most of them I found a solution or workaround. I didn’t receive many real problem records with Viewnify yet, so I hope that means it runs rather stable (not that users are so frustrated that they even won’t consider posting comments)

By: Ken Haggman

Ken Haggman — Wed, 16 Jan 2008 08:19:59 +0000

DXL has more (lots more) problems than just the occasional export error that may be due to poorly formed XML. NotesHound was from the start completely based around DXL but we have now abandoned DXL and are using other means to get the job done.

The worst problem, in my mind, is the instability of DXL. A piece of code may run 26 times against the same design element or document and work absolutely fine, and then - totally inexplainable - it will generate a DXL eporter error on the 27th run. The one gusess I can come up with for such behaviour is memory leaks.

By: Martin Vereecken

Martin Vereecken — Sat, 29 Dec 2007 16:14:23 +0000

Agree! Forms are worse than views. Only a lot of trial and error can help

By: Stephan H. Wissel

Stephan H. Wissel — Sat, 29 Dec 2007 13:39:02 +0000

DXL can be pretty challenging. While Views are relatively straight forward, forms are not. The XML follows the internal structure more than the idea of an XML file. E.g. a “run” element influences all following text instead of enclosing the text that is defined by a run. Also inside a run line breaks are actually line breaks, there is no “br” element.
stw