Davanum Srinivas wrote:
>
> > > The most common reason for this exception is that the driver was not loaded.
> > > Cocoon uses an initial parameter in the "web.xml" file to automatically load
> > > classes on startup. This way, the class is loaded only once and the
> > > server's
> > > time is spent doing more productive things. Make sure the following entry
> > > is in your "web.xml" file:
> > >
> > > <init-param>
> > > <param-name>load-class</param-name>
> > > <param-value>
> > > <!-- comma or whitespace separated list of fully qualified class names
> > > to load on startup.
> > > -->
> > > oracle.jdbc.driver.OracleDriver
> > > </param-value>
> > > </init-param>
> > >
> > > If the class is loaded correctly, and you are still getting this error,
> > > then there
> > > is probably an error in your connection information. The SQLException
> > > above is thrown when there are no open connections to the database.
> > >
> >
> > Even if placing JDBC drivers in the load-class param can be justified
> > from a design point of view (it's loaded only once, it's a deployment
> > parameter, etc), it appears that it is confusing users. This is mainly
> > because nearly all tools that rely on a JDBC connection (including C1)
> > ask for the JDBC url and driver class at the same time or place.
> >
> > What about allowing to optionally specify the driver class name in the
> > datasource configuration ?
>
> +1. How about post Beta2?
Actually, that requires a change to Avalon Excalibur--I can commit it to
CVS now. The new configuration element will be <driver>.
<jdbc name="personnel">
<driver>oracle.jdbc.driver.OracleDriver</driver>
<dburl>jdbc:oracle:thin:@host:1521:ORCL</dburl>
</jdbc>
S/MIME Cryptographic Signature
