XSLT - how to include snippets from other XSLT files?

(Continuing my theme of trying to understand how to do things in XSLT that were fairly easy to do in PTs...)
Environment[indent]TS 671SP1 Solaris 10 (or 672 W2K)
Using XSLT presentation templates - no Perl (sigh)[/indent]
Scenario[indent]I have a DCT which contains N fields of "common" content, and several fields of content that should only end up in the output if the DCR is being processed for a given target (vague, I know, but don't worry about it too much right now)
Currently, I have two XSLT files - one that formats all the common content, and one that formats all the common content plus the target-specific content. For reasons that I won't go into right now, I cannot use conditional coding within a single XSLT file for handling this target-specific aspect - I will have two (or more) registered XSLTs for the data-type. For example (the highlighted part is in one, but not the other XSLT file):

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" ...>
  <xslutput method="xml" indent="yes" .../>
  <xsl:template match="/record">
    <html>
      <xsl:call-template name="HEAD"/>
      <body>
          <xsl:call-template name="TOP"/>
<xsl:call-template name="TOP2"/>
          ...
          <xsl:call-template name="BOTTOM"/>
      </body>
    </html>
  </xsl:template>
  <xsl:template name="HEAD">
      <head>
        <title><xsl:value-of select="/record/title"/></title>
        ...
      </head>
  </xsl:template>
  <xsl:template name="TOP">
          <xsl:for-each select="/record/summary">
            <p><xsl:value-of select="."/></p>
          </xsl:for-each>
  </xsl:template>
<xsl:template name="TOP2">
          <xsl:for-each select="/record/special">
            <p><xsl:value-of select="."/></p>
          </xsl:for-each>
  </xsl:template>
  ...
  <xsl:template name="BOTTOM">
          <xsl:for-each select="/record/closing">
            <p><xsl:value-of disable-output-escaping="yes" select="."/></p>
          </xsl:for-each>
          ...
  </xsl:template>
</xsl:stylesheet>

If I have these as two distinct files, with all of the common code replicated within each file - it works just fine. However, as one might imagine, I'd rather move all those template definitions, after the first one, to a separate file so I don't have to replicate them. Essentially, I'm looking to do this (highly abridged):

<?xml version="1.0" encoding="utf-8"?>
<!-- XSLT-COMMON -->
<xsl:stylesheet version="1.0" ...>
  <xsl:template name="HEAD">...</xsl:template>
  <xsl:template name="TOP">...</xsl:template>
  <xsl:template name="TOP2">...</xsl:template>
  ...
  <xsl:template name="BOTTOM">...</xsl:template>
</xsl:stylesheet>

and:

<?xml version="1.0" encoding="utf-8"?>
<!-- XSLT-1 (XSLT-2) -->
<xsl:stylesheet version="1.0" ...>
  <xslutput method="xml" indent="yes" .../>
  <xsl:template match="/record">
    <html>
      <xsl:call-template name="HEAD"/>
      <body>
          <xsl:call-template name="TOP"/>
<xsl:call-template name="TOP"/>
          ...
          <xsl:call-template name="BOTTOM"/>
      </body>
    </html>
  </xsl:template>

[/indent]Problem[indent]I've tried various combinations of:

Find more posts tagged with

Comments

kaalraa

Hi Adam,

I had used xsl:include command in one of my template where it was being surrounded by xsl:if to check whether the DCT item has been given a value or not and it worked fine.

But could not say about the doubt you have about name attribute being used as i was having match attribute throughout.

(Continuing my theme of trying to understand how to do things in XSLT that were fairly easy to do in PTs...)

Environment[indent]TS 671SP1 Solaris 10 (or 672 W2K)

Using XSLT presentation templates - no Perl (sigh)
[/indent]Scenario[indent]I have a DCT which contains N fields of "common" content, and several fields of content that should only end up in the output if the DCR is being processed for a given target (vague, I know, but don't worry about it too much right now)

Currently, I have two XSLT files - one that formats all the common content, and one that formats all the common content plus the target-specific content. For reasons that I won't go into right now, I cannot use conditional coding within a single XSLT file for handling this target-specific aspect - I will have two (or more) registered XSLTs for the data-type. For example (the highlighted part is in one, but not the other XSLT file):
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" ...>
<xslutput method="xml" indent="yes" .../>
<xsl:template match="/record">
<html>
<xsl:call-template name="HEAD"/>
<body>
<xsl:call-template name="TOP"/>
<xsl:call-template name="TOP2"/>
...
<xsl:call-template name="BOTTOM"/>
</body>
</html>
</xsl:template>
<xsl:template name="HEAD">
<head>
<title><xsl:value-of select="/record/title"/></title>
...
</head>
</xsl:template>
<xsl:template name="TOP">
<xsl:for-each select="/record/summary">
<xsl:value-of select="."/>
</xsl:for-each>
</xsl:template>
<xsl:template name="TOP2">
<xsl:for-each select="/record/special">
<xsl:value-of select="."/>
</xsl:for-each>
</xsl:template>
...
<xsl:template name="BOTTOM">
<xsl:for-each select="/record/closing">
<xsl:value-of disable-output-escaping="yes" select="."/>
</xsl:for-each>
...
</xsl:template>
</xsl:stylesheet>
If I have these as two distinct files, with all of the common code replicated within each file - it works just fine. However, as one might imagine, I'd rather move all those template definitions, after the first one, to a separate file so I don't have to replicate them. Essentially, I'm looking to do this (highly abridged):
<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0" ...>
<xsl:template name="HEAD">...</xsl:template>
<xsl:template name="TOP">...</xsl:template>
<xsl:template name="TOP2">...</xsl:template>
...
<xsl:template name="BOTTOM">...</xsl:template>
</xsl:stylesheet>
and:
<?xml version="1.0" encoding="utf-8"?>

<xsl:stylesheet version="1.0" ...>
<xslutput method="xml" indent="yes" .../>
<xsl:template match="/record">
<html>
<xsl:call-template name="HEAD"/>
<body>
<xsl:call-template name="TOP"/>
<xsl:call-template name="TOP"/>
...
<xsl:call-template name="BOTTOM"/>
</body>
</html>
</xsl:template>
[/indent]Problem[indent]I've tried various combinations of:
<xsl:include .../>

<xsl:import .../>

<xsl:apply-templates .../>

<xsl:apply-imports .../>

But I cannot seem to get it to work.

I think it might have something to do with the fact that I'm using the '
name
' attribute for my templates elements instead of the '
match
' attribute - but I don't know.

Has anyone here successfully done imports/includes of XSLT like this? I.e. creating a "library" of named template "functions" that can be called in whatever order desired by an including XSLT file?
[/indent]

vy8359

Try xinclude:include href="include.xml" parse="xml"

Adam Stoller

Try xinclude:include href="include.xml" parse="xml"

I think I figured out a different approach that will work (I've been using it on some other stuff, haven't gotten back around to this original issue yet). Instead of trying to create a library that is pulled in and used from other XSLTs - create the monolithic block that contains everything and use conditional (xsl:if or xsl:choose/xsl:when/xsl Smiley Surprised

therwise) statements within there - and then when I include the master template pass param's that will be used within those conditionals.

If/when I get back to this original issue and try out what I'm talking about here, I'll post some updated code snippets.

getnaren

Have you tried mode?

I think I figured out a different approach that will work (I've been using it on some other stuff, haven't gotten back around to this original issue yet). Instead of trying to create a library that is pulled in and used from other XSLTs - create the monolithic block that contains everything and use conditional (xsl:if or xsl:choose/xsl:when/xsltherwise) statements within there - and then when I include the master template pass param's that will be used within those conditionals.

If/when I get back to this original issue and try out what I'm talking about here, I'll post some updated code snippets.

Adam Stoller

Have you tried mode?

I don't think so - basically the stuff I've been doing (which isn't the original stuff that spawned this thread) is largely concentrating on email header and body templates - and for these I'm using the model of having a generally fully-functional base XSL file like:[html]

[/html]And then a wrapper XSLT file that sets some parameters before "calling" the base XSLT file, like:[html]

[/html]This way, the wrappers can pre-set things like the subject_param and conditions regarding its value could then be performed in the base XSLT file.

This methodology seems to be working just fine for now, for the emails. If/when I get back to the FormsPublisher DCR processing, I'll see if the same methodology suffices.

(note: the XML being processed here is from slightly modified iwgetwfobj output since there is a bug in CSSDK that doesn't properly handle generating the XML information for grouptasks)

CRB

part of the discussion here was about how to include or import files into xslt pt. i havn't got the include or import directive to work, but this does the job:
it works with XalanTransform and url generate cmd.

[HTML]

or

[/HTML]