cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Allan Erskine <>
Subject Re: new c2 esql logicsheet checked in
Date Thu, 11 Jan 2001 16:11:42 GMT
> The Driver parameter is not needed in C2--the load-class init parameter
> the needed classes for drivers, protocol handlers, etc.

While you're in there, I noticed that in my version of cocoon (checked out
jan 8), my jdbc driver class was not being loaded for pages using

The form examples you checked in would only start working after a page with
the old esql:driver/username/password setup was loaded first...i checked it
all through with jdb, but i haven't really found my feet enough yet to be
thinking patches...(soon though i hope!)


----- Original Message -----
From: "Berin Loritsch" <>
To: <>
Sent: Thursday, January 11, 2001 1:27 PM
Subject: Re: new c2 esql logicsheet checked in

> Donald Ball wrote:
> > hi guys. i just checked in a new version of the c2 esql logicsheet that
> >
> > conforms to the final esql namespace schema. a few functions may be
> >
> > missing, i'll be adding them, but i finally got a working version so i'm
> >
> > checking it in. note that it differs from the c1 version by only one
> >
> > now - the namespace uri for xsp.
> >
> >
> >
> > (i almost think there's good reason to keep the xsp namespace uri the
> >
> > from c1 to c2... but c'e la vie.)
> I noticed that you reverted back to the driver, dburl, username, password
> in the sample.  I guess this is as good a time as any to point out a
> of things--since the use-connection is relatively new.
> The Driver parameter is not needed in C2--the load-class init parameter
> the needed classes for drivers, protocol handlers, etc.
> The use-connection parameter is IMHO much more desired--as someone who is
> being introduced to Cocoon can make one change in the cocoon.xconf file
> to make ALL the samples work.  I will test with that arrangement and
> the change to the samples.
> The important thing to note is that creating Connections EVERY TIME a page
> is requested is very costly--and there is no direct control over the
> of connections created at one time.  The JdbcDataSource Component takes
> care of this with a closed pool (it doesn't keep eating up resources,
> because it will dissallow connections beyond a certain number of
> connections.  This allows administrators to effectively plan the hardware
> and networking environment in a much more sane manner.
> So, I propose to make the use-connection parameter the officially prefered
> method of doing it--and making the dburl/user/password approach deprecated
> but still supported for backwards compatibility.  I also propose that all
> samples should use the prefered methodology due to the fact that most
> learning is following the examples we have here.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

View raw message