I would go one step further and not ship jdbc-related components in the basic distro :-), and bundle dbcp and jdbc-related code as a separate module.
If someone is using a database - there are few setup steps anyways, and downloading a separate tomcat module may be the easiest of them. From a tomcat-lite perspective, it would be great if the interfacing between the jdbc+dbcp code and tomcat would be lighter and not dependent on much catalina internals. Costin On Tue, Oct 21, 2008 at 8:02 AM, Remy Maucherat <[EMAIL PROTECTED]> wrote: > On Tue, 2008-10-21 at 10:19 -0400, Yoav Shapira wrote: > > However, I don't think we should stick a connection pool > > implementation in Tomcat proper. It should go in Commons DbUtils, or > > DBCP, or another existing project. Heck, it can even start out on > > Google Code, idealy with an ASL license. > > > > I don't want to bloat Tomcat with extra stuff, no matter how good. > > I'd much rather remove stuff and keep the core way smaller. I really > > like what Costin is doing with his "Tomcat lite." > > So you would not even ship one "default" connection pool, as we do now ? > > Rémy > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
