One way would be to upgrade to ASP.NET with its terrific XML support, and
use Saxon.NET which supports XSLT 2.0.
https://sourceforge.net/projects/saxondotnet/
NB1: Saxon.NET is an OS effort to port the great Saxon product to .NET and
Mono. All functionality offered has its origin in Saxon, therefore all
credits go to its creator, Michael Kay.
NB2: Saxon.NET is still an early beta product, and is currently about 25%
slower than using Saxon (on Windows). There is a workaround to this - you
can spawn processes in ASP.NET which run Saxon transformations in the
background and return to you the output, which is the same as running Saxon
from the command line, and thus has the same performance.
Cheers,
<prs/>
http://www.pietsieg.com
-----Original Message-----
From: António Mota [mailto:amsmota(_at_)gmail(_dot_)com]
Sent: Jueves, 10 de Marzo de 2005 11:26 a.m.
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] calling two consecutive xsl files
Let me ask a dumb question:
Against my will and advice, we're moving a lot of XSLTing from the client to
the server. But as a advantage, i'm no longer tied to transformiix and msxml
processors, nor to XSL 1.0.
But how do i do xsl on the server? Supose i use Saxon, how do i invoke a
transformation from a URI? Do i have to have some sort of scripting, or so?
Now we're building ASP to invoke XSLTs, but i want to break free of that,
and also want to embrace XSL 2.0 where i can.
Thanks.
On Thu, 10 Mar 2005 16:47:56 +0000, RQamar
<qamar_rahil(_at_)yahoo(_dot_)co(_dot_)uk> wrote:
Thanks Micheal
I was able to resolve my query using the 'saxon:next-in-chain' extension.
Rahil
Michael Kay wrote:
Pipeline processing was discussed on this list yesterday:
http://www.biglist.com/lists/xsl-list/archives/200503/msg00447.html
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: RQamar [mailto:qamar_rahil(_at_)yahoo(_dot_)co(_dot_)uk]
Sent: 10 March 2005 14:29
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] calling two consecutive xsl files
Hello again
Is it possible to do something like
Input.xml -> First.xsl -> Output1.xml -> Second.xsl ->
FinalOutput.xml
as one execution ?
At the moment my execution is in two stages. I do
Input.xml -> First.xsl -> Output1.xml
and then manually start the second execution
Output1.xml -> Second.xsl -> FinalOutput.xml
I was wondering whether something in my First.xsl could prevent me
from seeing Output1.xml. Some background processing could be done to
only throw the FinalOutput.xml as the end result.
Comments?
Thanks
Rahil
--~-----------------------------------------------------------------
- XSL-List info and archive:
http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--