You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2002/06/27 19:34:25 UTC
DO NOT REPLY [Bug 8734] -
ESQL Error in Cocoon 2.0.3-branch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8734>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8734
ESQL Error in Cocoon 2.0.3-branch
------- Additional Comments From peter.nuetzel@inglobo.de 2002-06-27 17:34 -------
I've experienced a similar problem:
org.apache.cocoon.ProcessingException: Language Exception:
org.apache.cocoon.components.language.LanguageException: Error compiling
edit_list_xsp:
Line 794, column 56: Missing term.
Line 794, column 56: ')' expected.
Line 0, column 0:
2 errors
the corresponding lines in the generated java source are:
789 xspAttr.addAttribute(
790 "",
791 "jahr",
792 "jahr",
793 "CDATA",
794 String.valueOf( EsqlHelper.getStringFromByteArray(default.getBytes (), ) )
795 );
which corresponds to the following snippet in the XSP:
<xsp:attribute name="jahr"><esql:get-string column="jahr"/></xsp:attribute>
the responsible template in esql.xsl is "get-string-encoded" (line 1034).
It seems that the variables/parameters references were interchanged:
$resultset points to $encoding and $column-spec is empty (or points to $null?)
So I think this is a Xalan Bug. With Xalan 2.2 the XSP works correctly.
(BTW with Xalan 2.4D1 my sitemap doesn't even compile)
I will look in the Xalan Bug database if there is s.th. filed which explains
this bug.
-peter
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org