Re: [xsl] Tricky inclusion match

Subject: Re: [xsl] Tricky inclusion match
From: Karl Stubsjoen <kstubs@xxxxxxxxx>
Date: Tue, 29 Mar 2005 11:35:33 -0700
Mukul:  was there a specific namespace decleration?  (and thanks for
the verification)


On Tue, 29 Mar 2005 09:55:49 -0800 (PST), Mukul Gandhi
<mukul_gandhi@xxxxxxxxx> wrote:
> Incidently I have .NET framework 1.1 installed. I just
> tested.. .NET class XslTransform supports node-set
> function(in exactly the same way as MSXSL)..
> 
> I tried this C# code..
> 
> XslTransform xslt = new XslTransform();
> xslt.Load(args[1]);
> XPathDocument xpathdocument = new
> XPathDocument(args[0]);
> XmlTextWriter writer = new XmlTextWriter(Console.Out);
> writer.Formatting=Formatting.Indented;
> xslt.Transform(xpathdocument, null, writer, null);
> 
> Regards,
> Mukul
> 
> --- Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> > Not sure if exsl:node-set is supported for .Net, can
> > someone please
> > verify if this should work in .NET?  I am using
> > other EXSLT /
> > GotDotNet extensions, like the date format
> > extensions.
> >
> > http://www.exslt.org/exsl/functions/node-set/
> >
> >
> >
> > On Tue, 29 Mar 2005 10:27:56 -0700, Karl Stubsjoen
> > <kstubs@xxxxxxxxx> wrote:
> > > Hmmm... bit of a dilema in that I am using .NET
> > EXSLT functionality in
> > > development but in production the true parser is
> > MSXML.
> > > So, I guess I am at a bit of a stumbling point
> > unless I can somehow
> > > use either/or functionality based on the
> > environment.
> > > ugggg...
> > > Could I have a base template who's rule for
> > evaluating/aggregating my
> > > variable derive from the MSXML's node-set but for
> > my .NET EXSLT
> > > functionality override this function and also
> > namespace (I guess) in
> > > order to aggregate the variable correctly?
> > > Karl
> > >
> > > On Tue, 29 Mar 2005 09:12:26 -0800 (PST), Mukul
> > Gandhi
> > > <mukul_gandhi@xxxxxxxxx> wrote:
> > > > > but I am faithful there is a very realistic
> > 1.0
> > > > solution!
> > > > It should be possible with XSLT 1.0.. Possibly
> > you
> > > > need to use node-set function also. You can
> > judge from
> > > > the solution I posted how relatively easy it is
> > with
> > > > XSLT 2.0 .. All the hard work is done by the
> > > > processor.
> > > >
> > > > > So, let me ask the following question:
> > > > > Use a variable to store the results of an
> > > > > apply-templates rule.  The
> > > > > result is a new element which might look
> > something
> > > > > like this:
> > > > > <data>
> > > > >   <value>1</value>
> > > > >   <value>1</value>
> > > > > </data>
> > > > >
> > > > > How can I aggregate (sum) the above data
> > element
> > > > > which is stored in a variable?
> > > > You would need to use node-set function as..
> > > > sum(node-set($temp)/data/value) . XSLT 1.0
> > does'nt
> > > > allow to treat result tree fragments as "node
> > sets"
> > > > (but XSLT 2.0 does) ; so in 1.0 we need to
> > convert RTF
> > > > to node set using node-set function..
> > > >
> > > > Regards,
> > > > Mukul
> > > >
> > > > > Karl
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Small Business - Try our new resources
> > site!
> > > > http://smallbusiness.yahoo.com/resources/
> >
> >
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 250MB free storage. Do more. Manage less.
> http://info.mail.yahoo.com/mail_250

Current Thread