Chuck wrote:
Not sure what else is going on, but the above is incorrect for your webapp - the
context name is *not* part of the url-pattern.
Oops! You're right of course. Thank you! I'm a little confused as to
why having an incorrect url-pattern would cause the SQL to fail.
About the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
On 3/8/2010 1:31 PM, Robert Jacobson wrote:
I managed to figure out a way to do it using a jdbc resource and
sql:query and sql:update tags in a couple JSP files.
Yuck :(
Well, the code works wonderfully when I don't have any security
Hi,
I'm running Tomcat 6.0.20 on Windows 2003 Server, with JRE 1.6.0_14.
I have a working Tomcat configuration using MySQL authentication to access to
ROOT webapp. I'm using DataSourceRealm just like the one in the Tomcat docs
From: Robert Jacobson [mailto:vvnxbdd...@snkmail.com]
Subject: Adding security constraint breaks sql functionality
--- BEGIN web.xml for /changepass
web-app
!-- Security constraint for the webapp --
security-constraint
web-resource-collection
web-resource-namechangepass Web