Um, you're preaching to the choir. My whole point is that we should all use the same database pool, if possible. I think it's unfortunate that Struts and Turbine are not on the same page. My suggested approach is that we create a utilities subproject that includes either the Turbine pool or the Struts pool and use it. That way, I can deploy the database pool and Turbine, the database pool and Struts, the database pool and both, or go off on my own merry way with just the database pool. Turbine is nice, but it's not me.
> -----Original Message-----
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 2:24 PM
> To: [EMAIL PROTECTED]
> Subject: Re: What is Jakarta?
>
>
> on 2/7/01 12:15 PM, "Morgan Delagrange" <[EMAIL PROTECTED]> wrote:
>
> > My mistake, although stating that you have a database
> > connection pool component does not imply that it is
> > applicable outside of Turbine.
>
> You could ask a very simple question:
>
> "Is Turbine's Connection Pooling code available for use
> outside of Turbine?"
>
> Oh wait, I forgot, it is easier to write a connection pool
> from scratch than
> it is to ask a simple question.
>
> :-(
>
> -jon
>
> --
> If you come from a Perl or PHP background, JSP is a way to take
> your pain to new levels. --Anonymous
> <http://jakarta.apache.org/velocity/> &&
> <http://java.apache.org/turbine/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
