This is definitely a problem for prepackaged WARs that expect DBCP to live under org.apache.tomcat.dbcp.dbcp and not org.apache.commons.dbcp. It would have been better if Tomcat wouldn't have "repackaged" those but we still need to come up with a solution...
Like you said, the workaround is to use tomcat-dbcp.jar from tomcat.apache.org.
This is definitely a problem for prepackaged WARs that expect DBCP to live under org.apache. tomcat. dbcp.dbcp and not org.apache. commons. dbcp. It would have been better if Tomcat wouldn't have "repackaged" those but we still need to come up with a solution...
Like you said, the workaround is to use tomcat-dbcp.jar from tomcat.apache.org.