Re: Down the rabbit hole with JDBC

2008-07-31 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt, Just a note: as you seem to be just getting started with everything, might I make the bold recommendation that you avoid doing any database work from JSPs? Databases are notoriously finicky when it comes to resource management (cleaning up

RE: Down the rabbit hole with JDBC

2008-07-27 Thread Martin Gainty
http://dev.mysql.com/doc/refman/5.0/en/connector-j-usagenotes-j2ee.html#connector-j-usagenotes-tomcat specifies these configurationparameters Context Resource name=jdbc/MySQLDB auth=Container type=javax.sql.DataSource/ !-- The name you used above, must match

Re: Down the rabbit hole with JDBC

2008-07-24 Thread David Smith
This isn't a JDBC error as much as it's a taglib error. You are trying to use JSTL taglibs in your web application and tomcat can't find the libraries that contain the taglib. Things to check: 1. standard.jar and jstl.jar are in the webapp's WEB-INF/lib directory -- at least for jstl 1.1.

Re: Down the rabbit hole with JDBC

2008-07-24 Thread Matt Burkhardt
Thanks - it was the first - I just had the files in the WEB-INF directory - not in the lib Is there some method for finding errors / logs? Right now, I'm trying to get an application running, and I'm just guessing. For example, my catalina.log file says INFO: The listener

RE: Down the rabbit hole with JDBC

2008-07-24 Thread Caldarale, Charles R
From: Matt Burkhardt [mailto:[EMAIL PROTECTED] Subject: Re: Down the rabbit hole with JDBC INFO: The listener org.alfresco.web.app.ContextListener is already configured for this context. The duplicate definition has been ignored. The above is a cosmetic error in 6.0.16; it does no damage

Re: Down the rabbit hole with JDBC

2008-07-24 Thread Ken Bowen
Matt, If you don't find anything suggestive in the logs, try running with a debugger and put a breakpoint on the first statement in the contextInitialized method in your AppListener to try to track down why it's dying (i.e., what's causing SEVERE: Error listenerStart). Then start