XML documents that define DHTMLX context menus and tool bars have dynamically configured elements. These documents are manually created and exist in the root and contain A4D tags.
I had the system working and then needed to change my approach to simplify, and because 4D's command DOM Parse XML source failed when XML was executable. Now I remember you recommending against making XML an executable document, and understand why. For XML documents to be served correctly to 4D's DOM Parse XML source they must not be executable, and they cannot contain A4D tags. Working through this with you I came to the conclusion that the dynamic XML documents can be named with ".a4d" and use set content type. I've tested these calls and they work in the DHTMLX calls. Please forgive my unnecessary request. Thank always for your support! David Ringsmuth -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Aparajita Fishman Sent: Thursday, December 30, 2010 10:55 AM To: [email protected] Subject: Re: [Active4d-dev] response headers > So the same dynamically created XML > documents loaded by DHTMLX using javascript calls are loaded by the 4D > command DOM Parse XML source. Forgive me, you still haven't made it clear exactly what is going on. I don't understand why you have made .xml an executable extension. Who is creating the XML documents? Are they being saved to disk after being created? Kind regards, Aparajita www.aparajitaworld.com "If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoy.org _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
