XSLTGeneral questions and answers about XSLT. For issues strictly specific to the book XSLT 1.1 Programmers Reference, please post to that forum instead.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the XSLT section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
I have to populate results of my transaction in a file and write this file into linux file system using XSL. Every time i have to open the file, update the file with transaction results and save it in linux file system. Please help me with this.
I am currently working in XML Spy 2007. am not sure with the saxon version in this tool. The targetted place where i will be putting this XSL to run is a SOA appliance which knows just a subset of xsl tags. I will develop xsl in XML spy and run the xsl in this appliance.
Out of extreme curiosity i just wanted to know if file processing is possible in xsl? just as we do in C or Java.
You can read documents using the document() function and in XSLT you can write them using the xsl:result-document instruction. But generally you will invoke an XSLT transformation from a host application, and the host application will be responsible for obtaining the input and disposing of the output. As I said before, consult the API documentation for your chosen product.
Our aim is to log transaction status in a file present in linux file system. the input to the xsl that we are going to consume is a soap response message sent by an application which tells if transaction is success or is a failure. we have to use the soap response and keep appending to a file the status of each transaction. So can we use the result-document to write to a file present remotely.
The appliance we use is a pure and pure xsl based one. No java or any other runtime.