Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <008901c07bf0$23e806b0$0179a8c0@spukny>
From: Allan Erskine <a.erskine@cs.ucl.ac.uk>
To: cocoon-dev <cocoon-dev@xml.apache.org>
References: <Pine.LNX.4.30.0101102358320.458-100000@localhost.localdomain>
 <3A5DB4C7.7070004@apache.org> <004d01c07be9$305c36c0$0179a8c0@spukny>
 <3A5DDDE1.8080705@apache.org>
Subject: Re: new c2 esql logicsheet checked in
Date: Thu, 11 Jan 2001 17:01:26 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

whoops!  sorry - missed the web.xml settings...thanks for that - I have the
org.postgresql.Driver class not the postgresql.Driver.  That's it working
now!

Thanks again
Allan

----- Original Message -----
From: "Berin Loritsch" <bloritsch@apache.org>
To: <cocoon-dev@xml.apache.org>
Sent: Thursday, January 11, 2001 4:22 PM
Subject: Re: new c2 esql logicsheet checked in


> Allan Erskine wrote:
>
> >> The Driver parameter is not needed in C2--the load-class init parameter
> >
> >
> > loads
> >
> >
> >> 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
> >
> > esql:use-connection
>
> The JDBC driver should be installed in the WEB-INF/web.xml file:
>
> the Init Parameter "load-class" loads all the drivers you need.  The class
names
> for the IBM WebSphere workaround, the Oracle JDBC driver, and the
PostgreSQL
> JDBC Driver are all in there.  Just add yours to the list.
>
> > 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!)
>
> I will have to document the process.
>
> The new esql logicsheet got updated by the original author (?), but was
basically
> the same for both C2 and C1.  The C2 version needed to be updated so that
the
> proper connection pooling was done.  I am waiting to be able to log in to
be
> able to actually check in the changes to make the <esql:pool> work (the
new
> name for use-connection).
>
> >
> >
> >
> > Allan
> >
> >
> >
> > ----- Original Message -----
> >
> > From: "Berin Loritsch" <bloritsch@apache.org>
> > To: <cocoon-dev@xml.apache.org>
> > 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
> >
> >>
> > line
> >
> >
> >>> now - the namespace uri for xsp.
> >
> >>>
> >
> >>>
> >
> >>>
> >
> >>> (i almost think there's good reason to keep the xsp namespace uri the
> >
> >>
> > same
> >
> >
> >>> 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
> >
> >
> > couple
> >
> >
> >> of things--since the use-connection is relatively new.
> >
> >>
> >
> >> The Driver parameter is not needed in C2--the load-class init parameter
> >
> >
> > loads
> >
> >
> >> 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
> >
> >
> > commit
> >
> >
> >> 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
> >
> >
> > number
> >
> >
> >> 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
> >
> >
> > simultaneous
> >
> >
> >> 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: cocoon-dev-unsubscribe@xml.apache.org
> >
> >> For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >
> > For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>