Forum OpenACS Development: Re: Invalid XML in XQL files

Posted by Bart Teeuwisse on
Yet another issue that we need to tackle soon is to drop libxml and switch to Zoran's tDom AOLserver module.  It was supposed to be "released any day now" late last summer so one would hope it's actually available now? 

Don, tDOM 0.7.5 was released 2002-11-27 and is available from It works great with AOLServer!

Let's switch over to tDOM. And now that we are on the subject of XQL files, could we please include an XQL DOCTYPE at the top of each XQL file? I can provide a DTD for the type. With a DOCTYPE in place XQL files are a snap to create/modify by hand when using Emacs.


Posted by C. R. Oldham on
Sorry if this has already been discussed.  Is tDOM a drop-in replacement for nsxml?
Posted by John Sequeira on

I've written a tiny compatibility layer mapping ns_xml commands to tdom commands as part of my portable.nsd effort.  It's not quite drop-in,  but close.

Posted by Jeff Davis on
As much as I hate having queries in a seperate file, I am not sure if pre-processing the tcl is such a good idea. If the first step in installing openacs is "compile the actual tcl scripts" I would have serious concerns that the we would see two things
  • Mysteriously broken code which would result from errors in the parser or quirks in the particular source tcl.
  • even more difficulty in merging improvements from particular sites back into the code base.
If it were a cleaner language or if we had a full parser I would not worry quite so much but regardless of how good the parser is, the later problem will remain.

I don't see a lot of evidence that the QD overhead is anything to be that concerned about relative to going to the DB in the first place.

I think there is probably a better argument for precompiling adp files rather than doing them on the fly, although there it is much clearer that what you are doing is compiling and no one would really be tempted to discard the adp's and work directly with the resulting code.