From bogus@does.not.exist.com  Sun Aug 10 16:54:49 2008
From: bogus@does.not.exist.com ()
Date: Sun Aug 10 16:54:53 2008
Subject: No subject
Message-ID: <mailman.0.1218401693.6996.zope-xml@zope.org>

routinely XMLTransform (and soon its successor zopexmlmethods) and
standard python XML tools.

I would also, probably, keep the xmlfile on the file system using
localFS or the like (ie externalFile).

Doing all this from external python code gives you, IMHO, a tremendous
flexibility.


>[...snip...]
> ZopeXMLMethods looks to be very specific to handling XSL transforms;
> ParsedXML, now that I have looked more deeply at it, seems
> focused on a
> ZMI interface to XML documents (though documentation indicates that it
> should be possible to use DTML to create and manipulate XML data).

Thats my understanding, too. I tend to use ZopeXMLMethods.

>
> Anyone, please correct me if I am mistaken in the above statements.
>
> At this point, the shortest route to get what I want appears
> to be to use
> TTW Python Scripts and just deal with Python's native XML
> capabilities...
> comments?

I would use external python code, as detailed above.

>
> Any advice and / or personal anecdotes about what has worked
> for you and
> what hasn't would be appreciated. As with many projects, I am
> up against a
> deadline already passed.
>

The above mentioned architecture has proveed for me very useful and easy
to mantain. I cannot, though, give you comment on performance, as my
user application profile is quite light (i.e. less than 5 concurrent
user on a xml base of less than 500 fragments). What for sure helps, is
having many small xml documents rather than few big documents. I learned
to automatically split imported xml document in subfolders, based on
some high level tag in your xml tree. This gives you the added
advantages of context sensitive (at folder level) search capabilities
out of the box using Zcatalog.

Hope this helps.

--peppo
PS: deadlines are already passed by definition. Othervise we would call
them lifelines :)



From bogus@does.not.exist.com  Sun Aug 10 16:54:49 2008
From: bogus@does.not.exist.com ()
Date: Sun Aug 10 16:54:53 2008
Subject: No subject
Message-ID: <mailman.1.1218401693.6996.zope-xml@zope.org>

 >>> dom
 <Document at 0x8d5a3a8>

How do I get back the XML string representation of dom? If this
was a ParsedXML document, I could do dom.index_html(), like this::

 >>> app.test_xml
 <ParsedXML at /test_xml>
 >>> app.test_xml.index_html()
 u'<?xml version="1.0" ?>\n<Customer id="Customer_1">.... etc

This isn't a persistent object, so I don't want to add a 
ParsedXML doc for it. Is there a straightforward way to get at 
the XML reprensentation?

Regards,
-- 
Jean Jordaan
http://www.upfrontsystems.co.za