cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathaniel Alfred" <>
Subject RE: esql logicsheet sometimes fails to transform elements
Date Mon, 08 Aug 2005 08:37:00 GMT
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.

If that is the case, try to refer to your logicsheet inside the XSP by 
<xsp:logicsheet location="path/to/sil.xsl"/>.

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 []
> 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("", 
> "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("", 
> "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.
> Here is the xsp page whose Java code is excerpted above:
> <xsp:page language="java"
>     xmlns:xsp=""
>     xmlns:xsp-request=""
>     xmlns:esql=""
>     xmlns:sil="">
>      <stats-categories>
>          <sil:query connection="CLAM" row-element="stats-category">
>              SELECT * FROM StatCategories ORDER BY Category
>          </sil:query>
>      </stats-categories>
> </xsp:page>
> <sil:query> expands to:
>   <esql:connection>
>       <esql:pool>CLAM</esql:pool>
>       <esql:execute-query>
>         <esql:query>SELECT * FROM StatCategories ORDER BY Category</esql:query>
>         <esql:results>
>           <esql:row-results>
>                 <stats-category>
>                   <esql:get-columns />
>                 </stats-category>
>           </esql:row-results>
>         </esql:results>
>       </esql:execute-query>
>     </esql:connection>
> Thanks for looking at this and for any suggestions you can give.
> By the way it doesn't seem to be a memory issue... the Tomcat and Cocoon 
> status pages say there is still a fair bit of free memory.
> Lars
This message is for the named person's use only. It may contain confidential, proprietary
or legally privileged information. No confidentiality or privilege is waived or lost by any
mistransmission. If you receive this message in error, please notify the sender urgently and
then immediately delete the message and any copies of it from your system. Please also immediately
destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the intended recipient.
The sender's company reserves the right to monitor all e-mail communications through their
networks. Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorised to state them to be the views of
the sender's company.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message