Dxl- exporter en importer problemen

Dxlexport en import heeft een groot aantal problemen.

Hieronder een opsomming van wat ik ben tegengekomen. In het engels omdat ik het ook op developerworks forum heb geplaatst:

I will note my findings beneath:Database dxlexport and import afterwards throws the following problems:

1.Lotusscript and Java code designelements( agents, libraries ) can not be opened by the designer client. It throws an error like: document is not signed.Workaround can be to get a document handle on those design elements and perform a .sign() on them. This will correct the problem.

2. Imported views are "corrupt". This can be noticed by opening the view in the designer client and saving it. This will cause the selection formula to be replaced by one of the column formula's. No known workaround but the problem is fixed in 7.0.3.

3. Javascriptlibraries are imported as a long string. If there is comment with "//" characters in the javascript this will cause the code to break. Workaround is to get all elements from the dxl export and replace the content of those tags. The correct replacemet should be: .replaceAll("\n","\r\n"). This will fix the import.

4. Stylesheet elements are sometimes appended by one or more random characters. In case of a xsl file this will cause the application to break. Workaround is to get all from the dxl, see if it handles a xsl file and do a replacement. The replacement should:a. base64decode the filedata contentb. replace everything after the tag with ""c. replace "\n" for "\r\n"d. base64decodeand add it to the dxl

5. Sometimes the dxlexporter adds elements to the dxl. It does this if it encounters characters which can not be translated to xml. If this happens within a formula the dxl looks like: .The content of the formula tag also gets scrambled.This causes the dxlimporter to throw an error because a formula element can not contain child elements. Removing the elements from the dxl will not help because then the dxl importer will break on the scrambled content of the element. No known workaround.

6. The dxl importer stumbles on some base64 encoded files from the dxl. This only happens on OS400. It does not matter where those base64 encoded files are. They can be attachments, fileresources, stylesheets or what ever.In case of the above event the dxl importer throws a NullPointer exception!!!One instance of this occuring was with a msxml.msi file in the fileresources of a database.

7. If there is passthru text on a form or page, and on the same designelement the older "["and "]"are used for tagging html, the dxlimport causes
tags to be placed on the desigelement when opened in a browser. Workaround is to open the designelements in the designer client and save them.These are some of the problems I encountered while working with DXL.

Conclusion: a complete roundtrip from dxlexport to dxlimport can not be performed without the loss of information.