cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Painter-Wakefield <>
Subject Re: ESQL conflict
Date Tue, 30 Sep 2003 15:30:37 GMT
It looks as if you have a java import (or <xsp:include>) for a class named 
"Object" that isn't java.lang.Object.  E.g., "org.omg.CORBA.Object".  In 
this case, the compiler can't tell which Object the ESQL code is looking 
for.  If the other Object class is declared by you, there is an easy 
workaround:  don't import the class, but instead fully specify the class 
each time you use it, e.g.,

instead of 
        Object blah;

        org.omg.CORBA.Object blah;

If you don't have control of the code doing the import, then you'll have 
to patch something.  It is fairly straightforward to replace the ESQL 
logicsheet with your own copy of it, with corrections.  Write back if you 
need instructions for this approach.


"Josep Riudavets" <>
09/30/2003 10:44 AM
Please respond to users

        To:     <>
        Subject:        ESQL conflict

Hello ...
I'm trying to add into an XSP page esql taglibs. But when I add the 
namespace <xmlns:esql=""> shows next error message:
org.apache.cocoon.components.language.LanguageException: Error compiling 
ERROR 1 (org/apache/cocoon/www/XSP/
    private SQLException _esql_exception = null;
    private StringWriter _esql_exception_writer = null;

// start error (lines 159-159) "The type Object is ambiguous for the 
argument obj of the method _esql_printObject"
            protected void _esql_printObject ( Object obj, AttributesImpl 
xspAttr) throws SAXException

// end error
               if ( obj instanceof List) {
           ListIterator j=((List)obj).listIterator();
  <parameter name="prefix" value="esql"/>
  <parameter name="uri" value=""/>
  <parameter name="href"
<jdbc name="conexionBBDD">
<pool-controller> max="10" min="5"</pool-controller>
File postgresql.jar are placed under /WEB-INF/lib
Best regards

View raw message