Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 26549 invoked from network); 30 Sep 2003 15:30:15 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 30 Sep 2003 15:30:15 -0000 Received: (qmail 38803 invoked by uid 500); 30 Sep 2003 15:29:57 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 38787 invoked by uid 500); 30 Sep 2003 15:29:57 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 38773 invoked from network); 30 Sep 2003 15:29:57 -0000 Received: from unknown (HELO thorin.duhs.duke.edu) (152.16.195.18) by daedalus.apache.org with SMTP; 30 Sep 2003 15:29:57 -0000 Received: from strider.notes.duke.edu (strider.notes.duke.edu [152.16.19.13]) by thorin.duhs.duke.edu (8.12.10/8.12.10) with ESMTP id h8UFTcD5000433 for ; Tue, 30 Sep 2003 11:29:38 -0400 (EDT) To: users@cocoon.apache.org Subject: Re: ESQL conflict MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 Message-ID: From: Christopher Painter-Wakefield Date: Tue, 30 Sep 2003 11:30:37 -0400 X-MIMETrack: Serialize by Router on strider.notes.duke.edu/DUMC_Services/mc/Duke(Release 6.0.2CF1|June 9, 2003) at 09/30/2003 11:29:58, Serialize complete at 09/30/2003 11:29:58 Content-Type: multipart/alternative; boundary="=_alternative 00553D9E85256DB1_=" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --=_alternative 00553D9E85256DB1_= Content-Type: text/plain; charset="us-ascii" It looks as if you have a java import (or ) 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 org.omg.CORBA.Object .... Object blah; do 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. -Christopher "Josep Riudavets" 09/30/2003 10:44 AM Please respond to users To: cc: Subject: ESQL conflict Hello ... I'm trying to add into an XSP page esql taglibs. But when I add the namespace shows next error message: org.apache.cocoon.components.language.LanguageException: Error compiling procesa_xsp: ERROR 1 (org/apache/cocoon/www/XSP/procesa_xsp.java): ... 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(); Cocoon.xconf: .... org.postgresql.Driver

max="10" min="5"

jdbc:postgresql://localhosto:5432/CAD josep mypassword Web.xml

load-class

org.postgresql.jar

File postgresql.jar are placed under /WEB-INF/lib Best regards --=_alternative 00553D9E85256DB1_= Content-Type: text/html; charset="us-ascii"
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
<xsp:include>org.omg.CORBA.Object</xsp:include>
....
Object blah;

do
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.

-Christopher

"Josep Riudavets" <jriudavetsa@uoc.edu>

09/30/2003 10:44 AM
Please respond to users

To: <users@cocoon.apache.org>
cc:
Subject: ESQL conflict

Hello ...

I'm trying to add into an XSP page esql taglibs. But when I add the namespace <xmlns:esql="http://apache.org/cocoon/SQL/v2"> shows next error message:

org.apache.cocoon.components.language.LanguageException: Error compiling procesa_xsp:
ERROR 1 (org/apache/cocoon/www/XSP/procesa_xsp.java):
...
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();
Cocoon.xconf:

<builtin-logicsheet>
<parameter name="prefix" value="esql"/>
<parameter name="uri" value="http://apache.org/cocoon/SQL/v2"/>
<parameter name="href"
value="resource://org/apache/cocoon/components/language/markup/xsp/java/esql.xsl"/>
</builtin-logicsheet>

....

<datasources>
<jdbc name="conexionBBDD">
<driver>org.postgresql.Driver</driver>
<pool-controller> max="10" min="5"</pool-controller>
<dburl>jdbc:postgresql://localhosto:5432/CAD</dburl>
<user>josep</user>
<password>mypassword</password>
</jdbc>
</datasources>

Web.xml

<init-param>
<param-name>load-class</param-name>
<param-value>org.postgresql.jar</param-value>
</init-param>

File postgresql.jar are placed under /WEB-INF/lib

Best regards

--=_alternative 00553D9E85256DB1_=--