Re: Does Resin still support the old way of setting up the database pool?

remember that huge changes occurred between 2.0 beta and 2.1

--
-Chris Beck - Coradiant, Inc - Research & Development - +1.514.908.6314-
-- www.coradiant.com - Technical foresight driving Internet economics --
------- This email represents my opinion, not that of Coradiant. -------
"The more laws and order are made prominent, the more
thieves and robbers there will be." -- Lao Tsu
Scott,
You said:
I believe that's due to the new jdbc-ext.  Resin itself doesn't
implement anything having to do with the RowSet, but it's included as
part of the JDBC 3.0 API.
I am using a 2.0 driver - byt anyway I am not sure what is the solution is?
Why does it work fine with Resin 2.0 and not 2.1.4?
Thanks,
Stef
----- Original Message -----
From: "Scott Ferguson" <ferg@xxx.com>
To: <resin-interest@xxx.com>
Sent: Tuesday, September 24, 2002 2:51 PM
Subject: Re: Does Resin still support the old way of setting up the
database
pool?
> stefan wrote:
> > Hi,
> >
> > I am presently trying to move resin from 2.0 to 2.1.4 and have run into
a
> > couple of problems.
> >
> > 1. I use the old way of creating the database pool - is this still
> > supported?
> >
> > <dbpool.sql id='myWebApp'
> > driver="com.ashna.jturbo.driver.Driver"
> > url="jdbc:JTurbo://10.10.10.2/myWebApp/sp = false"
> > user="masterUser"
> > password="myPass"
> > max-connections="25"
> > enable-transaction="true"
> > sql70="true" />
>
> Yes, but you shouldn't use it.
>
> >
> > 2. Any beans that use an implementation of a JDBC rowset causes Resin
to
> > choke on compile:
> >
> > C:\Documents and Settings\Administrator\Desktop\Java
> >
Code\Resin\resin-2.1.4\webapps\mySite\WEB-INF\classes\com\mySite\dataBaseBea
> > n.java:417:
> > class com.ashna.jturbo.rowset.JTurboRowSet is an abstract class. It
can't
> > be instantiated.
> >     JTurboRowSet crset = new JTurboRowSet();
> >
> > This error does not occur within Resin 2.0 b2.
>
> I believe that's due to the new jdbc-ext.  Resin itself doesn't
> implement anything having to do with the RowSet, but it's included as
> part of the JDBC 3.0 API.
>
> >
> > 3. I then just compile the classes myself and drop in the class files
in
the
> > webapps WEB-INF/classes folder and then I get this error:
> >
> > Error Message:
> >
> > Unresolved compilation problems: The import com.caucho cannot be
resolved
>
> DBPool is in com.caucho.sql.
>
> You really shouldn't be using it, though.
>
> Use DataSource with a JNDI lookup instead.
>
> -- Scott
>
> > DBPool cannot be resolved or is not a type DBPool cannot be resolved
DBPool
> > cannot be resolved or is not a type DBPool cannot be resolved DBPool
cannot
> > be resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved DBPool cannot be
> > resolved or is not a type DBPool cannot be resolved
> >
> > I did not have these errors in Resin 2.0 b1 .
> >
> > Any help would be appreciated.
> >
> > Stef
> >
>
>
>