On Sun, Mar 23, 2008 at 6:29 AM, Mark Thomas <[EMAIL PROTECTED]> wrote: > Costin Manolache wrote: > > I understand people using JDBC authenticator would miss the connection > > pooling - but maybe they could download it separately ? Would't be > > easier to just download the 'official' version ? > > No. commons-dbcp supports far more than just pooling for the JDBC > authenticator. The reason we do the renaming is to avoid class loading > issues when users want to use a Tomcat-managed connection pool alongside an > application that uses commons-dbcp and/or commons-pool directly. > > > > I'm also curious, assuming JDK1.5 is used to compile - would the > > tomcat distro work in JDK1.6 if dbcp is compiled with 1.5 ? > > Yes it does. To be more accurate, I haven't seen any issues using the > re-packaged DBCP on 1.6. > > > > In any case - it kind of sucks to not be able to build following the > > instructions ( ant download, ant ) - I didn't find any ref that JDK1.6 > > is not supported for build. > > Correct. > > If you want to fix this you could always port the DBCP build fixes from > commons. >
This isssue is being tracked as DBCP-191. Comments, suggestions, patches are welcome on the ticket or on commons-dev. Opinions on JDK support levels/branching from tomcat perspective would be appreciated. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
