Thanks for your answer.
I've tried xsp < esql < mystylesheet and xsp < mystylesheet < esql
and none worked...
It seems that order in namespace declaration is no longer taken into consideration...
Any other idea ?
-- Olivier BILLARD
Tim Myers wrote:
The stylesheets get chained together in a pipeline one after the other. The
only issue of one stylesheet using another is order in the pipeline. Your xsp must be transformed by any logicsheet that uses another logicsheet before it
is transformed by that other logicsheet. xsp.xsl is the least dependent, most
depended logicsheet. esql uses it.
Here's the part i'm not sure about:
Which ever order they are declared in cocoon.xconf is the order you should declare your logicsheet in:
yourlogicsheet > esql > xsp
or xsp < esql < yourlogicsheet.
There was once a time when processing order was determined by the order the namespaces appear on the root element. I don't think that is any longer the case.
Tim
On Thu, Jul 17, 2003 at 04:23:38PM +0200, Olivier Billard wrote:
Hi all !
I've already asked this question on the users list, but the dev-ers may be more able to answer... :)
I would like to know if there is any issue in using tablibs from built-in stylesheets (like esql) in user-custom built-in stylesheets.
For me, no Java code is generated...
Isn't it possible ?
How does Cocoon deal with all these built-in stylesheets ? A global stylesheet with "xsl:import" or "xsl:include" ? Is there a requiered order of declaration in cocoon.xconf to be able to cross-use taglibs ?
Thanks in advance !
-- Olivier BILLARD
