NotesDXLImporter is more than 4 years old. 4 year old should be able to speak.

It currently only can utter this "DXLImport operation failed message". It could do much better.

I work quite a lot with Java open Source frameworks with truckloads of xml. When there is an err in one of those xml files, I get somewhere in the stack trace a message like: "non-valid xml, because of line x, column y". Or "element abc  on line  x doesn't honour the dtd or the xml-schema". It would be realy boost productivity, if DXLImport were becomming a bit more talkative.

Especially as there are some issues which are not too obvious like:

1. this is not accepted:

<databasescript xmlns='http://www.lotus.com/dxl' default='false' private='false' noreplace='false' useapplet='false' treatashtml='false'> <code event='options'><lotusscript></lotusscript></code>

2. this is accepted: <databasescript xmlns='http://www.lotus.com/dxl' default='false' private='false' noreplace='false' useapplet='false' treatashtml='false'> <code event='options'><lotusscript> </lotusscript></code>

Contest-Question for promoters and demoters: Why does 1) fail and 2) pass?