yes. You're welcome!
| "Josep Riudavets" <[EMAIL PROTECTED]>
09/30/2003 11:46 AM
|
To: <[EMAIL PROTECTED]> cc: Subject: Re: ESQL conflict |
Ok Cristopher ... you're all right !!!
I'm using iaik.ixsil.core.* ... it implies many classes, and one of them is iaik.ixsil.core.Object, that conflicts with the other object class.
Now, I have declared every iaik.ixsil.core.xxx separately (does exist this word??)
Thanks a lot !!!
----- Original Message -----
From: Christopher Painter-Wakefield
To: [EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 5:30 PM
Subject: Re: ESQL conflict
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
