We're going to switch to using tDOM as our standard XML parser throughout the toolkit and this approach will allow us to avoid having to jump through any painful hoops in an attempt to mimic Oracle's java-based XML support in PostgreSQL.
There's already an AOLserver module that's been written by the author of tDOM and everything I've read/heard suggests that both are excellent pieces of work.
If you work your way through
this thread you'll see that Bart Teuwisse has already been using tDOM with AOLserver/OpenACS 4 with no problem whatsoever.
Originally we'd hoped to switch from ns_xml to tDOM for 4.6 but the AOLserver module release was delayed late summer/early fall so we dropped it as a 4.6 work item. We're definitely switching soon, though! For now there's no reason I know of that prevents you from loading the ns_xml module (for existing OpenACS 4.6 code) and tDOM (for forward-looking XML-handling code that you want to be compatible with 4.7)
