cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lock, Fred" <>
Subject [C2] Trouble with <xsp:include> tags in taglib
Date Fri, 20 Oct 2000 00:04:04 GMT
I'm having trouble with the <xsp:structure> and <xsp:include> tags under C2.
The trouble is that when I look in the repository at the generated java
class file for my xsp, the required import statement is not included.

It's as if C2 applies xsp.xsl to the xsp page before applying my custom
taglib. I say this because if I put the <xsp:structure> and <xsp:include>
tags in the xsp itself, then cocoon generates the import statement in the
output java class. However, I don't want to do this in the xsp. I don't want
my xsp's to have to know what they need to import.

Any suggestions? The code that does not generate the import statement is
included below.

Fred J. Lock
Lead Developer
HealthCast, LLC

// Here's my xsp:

<?xml version="1.0" encoding="ISO-8859-1"?>


// Here's my taglib:

<?xml version="1.0"?>


  <xsl:template match="xsp:page">

      <!-- This should generate an import in the output java class, -->
      <!-- but it doesn't -->

        <xsl:apply-templates select="@*"/>



  <!-- hello -->
  <xsl:template match="message:hello">
    Hello, World!

  <xsl:template name="get-nested-content">
    <xsl:param name="content"/>
      <xsl:when test="$content/*">
        <xsl:apply-templates select="$content/*"/>
      <xsl:otherwise>"<xsl:value-of select="$content"/>"</xsl:otherwise>
  <xsl:template match="@*|*|text()|processing-instruction()">
      <xsl:apply-templates select="@*|*|text()|processing-instruction()"/>

View raw message