Nathaniel Alfred wrote:
I see three possible causes for this behaviour:
1) The esql logicsheet is not applied (Cocoon problem).
2) The esql logicsheet is applied but does not transform the input (XSLT
problem).
3) The esql logicsheet is applied before sil.xsl.
If you define sil.xsl as <builtin-logicsheet> in cocoon.xconf, 3) is a likely
explanation. The order for builtin logicsheets is not defined since it is
derived from the namespace declaration on the xsp:page root element.
Thank you! This is a helpful suggestion. I had not thought of wrong
order of application of logicsheets as a possible cause for this
behavior, but it seems plausible. We do define sil.xsl as a
<builtin-logicsheet> in cocoon.xconf.
If that is the case, try to refer to your logicsheet inside the XSP by
<xsp:logicsheet location="path/to/sil.xsl"/>.
What does this do?
I was unable to find any documentation on the <xsp:logicsheet> tag, but
from what I see in the XSP core logicsheet, <xsp:logicsheet> is ignored.
Lars
If that is not the case, try to use another XSLT processor to exclude 2).
NB make sure that you pick up the Xalan version bundled with Cocoon and
not the one from JDK1.5.
HTH, Alfred.
-----Original Message-----
From: Lars Huttar [mailto:[EMAIL PROTECTED]
Sent: Freitag, 5. August 2005 21:37
To: Cocoon Users List
Subject: esql logicsheet sometimes fails to transform elements
Dear Cocoon users,
We have been struggling with a significant problem lately on our Cocoon
servers. It seemed to start around the time we upgraded to JDK 1.5 /
Tomcat 5.5.9 / Cocoon 2.1.7.
The problem involves XSP pages that use esql. Often they work fine, but
sometimes the esql logicsheet just doesn't seem to run. (Both behaviors
can occur with the some XSP page.) The output of the xsp page, instead
of including data produced by the esql query, includes the <esql:*> tags
themselves. The generated Java code includes things like:
this.contentHandler.startElement("http://apache.org/cocoon/SQL/v2";,
"query", "esql:query", xspAttr);
xspAttr.clear();
this.characters("\n SELECT * ");
this.characters("\n FROM StatCategories");
this.characters("\n ORDER BY Category");
this.characters("\n ");
this.contentHandler.endElement("http://apache.org/cocoon/SQL/v2";,
"query", "esql:query");
I should mention that we're also using a homegrown logicsheet (sil.xsl)
that generates the <esql:*> elements. However I'm sure that is not the
source of the problem. Many other stylesheets using sil.xsl work fine,
and even the ones that have problems used to work fine, and still do
sometimes (without code changes).
We have not yet seen a pattern in which xsp pages will fail at any given
time. Sometimes a page will work on machine A but not machine B; then
later the reverse will be true!
The problem occurs across multiple Cocoon applications, so it's a pretty
serious issue for us.
We have not yet upgraded our production environment to these versions,
and as far as I know, the production environment has not been affected
by this problem. If we can't resolve the problem, we may have to roll
back to Tomcat 4.1 and Java 1.4.2.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
