<< My experience is that XSLT is not designed to handle non-XML source data, and so struggles in this area.
Performance can alos be an issue in high-volume situations. For a data warehouse project; i.e., large volumes of information, the developers started with XSLT and ran into a bottleneck. They rewrote the transformations in Java. When the volume increased to 2000 XML documents per minutes, they migrated to C++. ------ XML/edi Group Discussion List ------ Homepage = http://www.XMLedi-Group.org Unsubscribe = send email to: [EMAIL PROTECTED] Leave the subject and body of the message blank Questions/requests: [EMAIL PROTECTED] To receive only one message per day (digest format) send the following message to [EMAIL PROTECTED], (leave the subject line blank) digest xmledi-group your-email-address To join the XML/edi Group complete the form located at: http://www.xmledi-group.org/xmledigroup/mail1.htm
