Write your own xsp.xsl and change "core-logicsheet" in cocoon.xconf (I don't think
it will be compliant with future versions of cocoon)
or quick and dirty way - write your own taglib like that:
<xsl:template match="/xsp:page/*[not(starts-with(name(.), 'xsp:'))][1]">
<xsp:structure>
<xsp:include>...<xsp:include>
</xsp:structure>
<xsp:logic>
private void your_method()
{
...
}
</xsp:logic>
<!-- Fist element processing from XSP page -->
<xsl:element name="{name()}">
<xsl:apply-templates/>
</xsl:element>
</xsl:template>
I'm using the last one and its works fine.....
Good luck,
Alex.
----- Original Message -----
From: "Argyn Kuketayev" <[EMAIL PROTECTED]>
To: "Cocoon-Users (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, June 25, 2002 3:48 PM
Subject: how to make XSP to extend the abstract class?
suppose, I've many methods which I want to share between XSP pages. I put
them all in the abstract class, then make Java class (generated from XSP) to
extend this abstract class. How?
thanks,
Argyn
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
