PATCH (Xalan 1.2): XRTreeFrag nodeset()

[Ovidiu Predescu <ov...@cup.hp.com>]

Hi,

I'm posting this patch again as the subject of the thread under which I posted
it may be misleading.

This patch allows applying templates on a tree fragment, which could be the
value of a variable for example. Here's an example:

<xslt:template match="page[split]">
 <xsl:variable name="page">
  <page>
   <xsl:apply-templates select="preceding::split"/>
  </page>
 </xsl:variable>
 <xsl:apply-templates select="$page"/>
</xsl:template>

The patch implements nodeset() to XRTreeFrag.

Regards,
-- 
Ovidiu Predescu <ov...@cup.hp.com>
http://orion.nsr.hp.com/ (inside HP's firewall only)
http://www.geocities.com/SiliconValley/Monitor/7464/

Re: PATCH (Xalan 1.2): XRTreeFrag nodeset()

[Gary L Peskin <ga...@firstech.com>]

> Ovidiu Predescu wrote:
> >
> > Hi,
> >
> > I'm posting this patch again as the subject of the thread under which I posted
> > it may be misleading.

And I meant to add to my previous post my thanks for submitting this
proposed change.

Gary

Re: PATCH (Xalan 1.2): XRTreeFrag nodeset()

[Gary L Peskin <ga...@firstech.com>]

Ovidiu Predescu wrote:
> 
> Hi,
> 
> I'm posting this patch again as the subject of the thread under which I posted
> it may be misleading.
> 
> This patch allows applying templates on a tree fragment, which could be the
> value of a variable for example. Here's an example:
> 
> <xslt:template match="page[split]">
>  <xsl:variable name="page">
>   <page>
>    <xsl:apply-templates select="preceding::split"/>
>   </page>
>  </xsl:variable>
>  <xsl:apply-templates select="$page"/>
> </xsl:template>
> 
> The patch implements nodeset() to XRTreeFrag.

Ovidiu ---

XalanJ1 has a nodeset extension built into it already.  Your proposed
patch could allow result tree fragments to be automatically treated like
node-sets.  This is not permitted by the XSLT 1.0 standard so it is
probably not something we'd want to incorporate into the base Xalan.  If
I've misunderstood something, please let me know.

Gary