JSP's not recompiling

[Johnson, David]

We're having some issues with JSP files not being recompiled when they
should be, and was wondering if anyone can shed some light on it.

We have Jasper set up in development mode, with the following in
conf/web.xml:

servlet
servlet-namejsp/servlet-name
 
servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class
init-param
param-namefork/param-name
param-valuefalse/param-value
/init-param
init-param
param-namedevelopment/param-name
param-valuetrue/param-value
/init-param
init-param
param-namemodificationTestInterval/param-name
param-value0/param-value
/init-param
init-param
param-namereloadable/param-name
param-valuetrue/param-value
/init-param
init-param
param-namexpoweredBy/param-name
param-valuefalse/param-value
/init-param
load-on-startup3/load-on-startup
/servlet

The JSP files are being created and updated by a content management
system on a remote box, and then pushed onto the webserver using Rsync. 

Tomcat does not always seem to spot that a file has been updated though,
and continues to serve the old jsp. I can force a recompile by
touching the jsp file, but have no idea why this works, as the rsync
is updating the timestamps whenever the page is updated anyway. 

Any advice would be welcome, it's driving our developers a little mad
and me with it.

Dave 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Auto-deploying to multi-level context paths

[Johnson, David]

Is there any way to set up an application so that the auto-deployer will
place it at a context path containing more than one level?

For example, I want my application at /hr/policies.

I can setup the context like this in server.xml, but this is bad because
I would need a server restart to change anything. 

I can also set it up in conf/Catalina/localhost as hr#policies.xml,
which seems to work okay (hurrah for mailing lists archives, as this
feature seems to be entirely absent in the docs). However this means
server admin intervention is required whenever our developers come up
with a new app.

Does anyone know of a way to make the auto-deployer deploy to a
multi-level context path, via META-INF/context.xml, or by naming the
application directory in a certain way (hash trick doesn't work there as
far as I can tell), or is it simply impossible? 

Cheers
Dave

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]