Hi Antonio,
At 12:00 PM 6/2/2004, you wrote:
Citando Pieter Reint Siegers Kort :
> The question is WHAT you want to do... please provide more information!
Weel, i have a xslt that is getting bigger and bigger
<xsl:template match="/">
<XPage class="Tester">
<Components>
<xsl:apply-templates select="/Formatos/Forms/Form[1]" />
<xsl:apply-templates select="/Formatos/Forms/Form[1]/Campos" />
(...)
</Components>
<Events>
<Event method="changeValue" target="btnProceed" type="ActionHandler"
/>
<Event method="addNewRecord" target="btnAddNew" type="ActionHandler"
/>
(...)
</Events>
<Data>
<Bind target="tblOne" source="Empreitada" />
(...)
</Data>
</XPage>
</xsl:template>
and wanted to put it like
<xsl:template match="/">
<XPage class="Tester">
<xsl:include href="xcomponents.xsl" />
<xsl:include href="xevents.xsl" />
<xsl:include href="xdata.xsl" />
</XPage>
</xsl:template>
Maybe i've overlooked something, but i'm not much experienced in XSL.
You might be overlooking named templates. For example you could have a
template "make-data":
<xsl:template name="make-data">
<Data>
<Bind target="tblOne" source="Empreitada" />
(...)
</Data>
</xsl:template>
and then call it with <xsl:call-template name="make-data"/>.
These are most useful when you have code that needs to be reused, but
modularity is another advantage.
These can also be managed in separate files and made available using the
usual xsl:include or xsl:import features.
Thanks.
Sure thing -- enjoy,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================