cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Heinicke (JIRA) <j...@apache.org>
Subject [jira] Kommentiert: (COCOON-1691) ESQL compilation error
Date Mon, 21 Nov 2005 18:26:42 GMT
    [ http://issues.apache.org/jira/browse/COCOON-1691?page=comments#action_12358178 ] 

Jörg Heinicke commented on COCOON-1691:
---------------------------------------

SVN commit 234125 (http://svn.apache.org/viewcvs.cgi?rev=234125&view=rev) obviously broke
this. I wonder if this could be better encapsulated or if all stylesheets generating Java
have to be changed when renaming such a variable like xspAttr. Alfred?

> ESQL compilation error
> ----------------------
>
>          Key: COCOON-1691
>          URL: http://issues.apache.org/jira/browse/COCOON-1691
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: XSP
>     Versions: 2.1.8
>     Reporter: Feliciano Borrego
>     Priority: Critical
>  Attachments: xsp_esql-error.zip
>
> In the Cocoon 2.1.7 version the sent file mis_referencias.xsp compiled and run correctly.
> org.apache.cocoon.components.language.LanguageException: Error compiling mis_referencias_xsp:
> ERROR 1 (org\apache\cocoon\www\file_\c_\Des\Proy\SigPortal\web\portal\xsp\mis_referencias_xsp.java):
> ...
> );
> _xspAttr.clear();
> // start error (lines 687-687) "xspAttr cannot be resolved"
> this._esql_printObject(_esql_struct[_esql_k],xspAttr);
> // end error
> this.contentHandler.endElement(
> "",
> "sql-row-item",
> ...
> ERROR 2 (org\apache\cocoon\www\file_\c_\Des\Proy\SigPortal\web\portal\xsp\mis_referencias_xsp.java):
> ...
> // postgres is broken as it doesn't allow getObject()
> // to retrieve any type (i.e. bit and bit varying)
> // so don't handle complex types different for postgres
> if (!_esql_connection.getURL().startsWith("jdbc:postgresql:")) {
> // start error (lines 713-713) "xspAttr cannot be resolved"
> this._esql_printObject(_esql_query.getResultSet().getObject(_esql_i), xspAttr);
> // end error
> break;
> }
> default:
> ...
> Line 687, column 0: xspAttr cannot be resolved
> Line 713, column 0: xspAttr cannot be resolved

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message