[COCOON-1691] ESQL compilation error

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.8
• Fix Version/s: 2.1.9
• Component/s: Blocks: Databases
• Assignee: Alfred Nathaniel
• Reporter: Feliciano Borrego
• Created: 22/Nov/05 01:51
• Updated: 08/Dec/05 17:05
• Resolved: 02/Dec/05 06:42

Description

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