Hi.
I just struggled with this and here's what I've determined so far. It
depends on where your context xml file lives:
1) If your context XML file is named via the convention
$CATALINA_HOME/conf/[enginename]/[hostname]/[contextname].xml, then you're
fine. Note that the file name is named afte
Hi.
I'm using 5.5.9 and have two contexts. One I'd like to use for production,
so I'd like to disable JSP checking by setting Tomcat's web.xml
"development" param for JspServlet to "false". But the second context I'd
like to use the JSP checking because it's a customer staging area where I'd
li
Hi.
I'm using Tomcat 5.5.9 and MySQL 5.0.17 and here's what my relavent file
sections look like (I've chaned the real app name to "foo", so notice where
"foo" occurs):
Note that you're missing the "name" and "factory" attributes, but I suspect
"name" is more the culprit.
In my WEB-INF/web.xml
Using the Jasper2 task and pointing it to my web.xml, the generated
fragment is automatically merged into the right spot of web.xml.
Here's how I specify the Jasper2 task. You'll obviously have to set your
attributes according to your setup. The two key attributes are
webxmlfragment and addwebxm
For anyone who's experiencing this, here's what's happening:
ContextConfig.java contains a method called "antiLocking" that tests to see
if your context in server.xml has "antiResourceLocking=true". If it does,
it creates a new directory calculated by 'deploymentCount++ + "-" + docBase
' in the
Hi.
I've got a Tomcat 5.5.9 app which takes uploaded files and puts them into a
directory according to this formula: app's root dir + "/photos".
So the dir in my case is "c:\tomcat\webapps\ROOT\photos\".
However, I've just noticed that the whole ROOT context directory gets
copied to Tomcat's tem
