> > It seems to me (from document fragments and example code) that the 'XML > > integration' has mostly targetted the XSLT transformations. > > > > It's maily intended for transforming it and generating output. For now this > means mainly XSLT.
Ahh, perhaps I am starting to get it. Basically the XSLT recipes configure the processing of the code to use XML libraries, and when you do an Execute on them, they make the calls using the specified XML library (libxml2 in my case). So all the XSLT functionality is done by the respective libraries, and Embperl makes the necessary calls to these by wrapping these in perl code to conform to the Embperl API. So all Embperl really knows is the correct way to call the few necessary functions from the XML library to parse and get the XSLT done. Nice That close? > > - Should I just use an outside complete-perl solution, which is simply > > 'use'd from within my Embperl code? > > Yes, just use XML::LibXML or anything similar Great! Just wanted to make sure I was not reproducing functionality that already existed. Cameron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
