Using JBoss 2.4.4 + Jetty, I can deploy an unpacked, expanded directory by pointing the
autodeployer in the jboss.jcml to that particular directory.  I try the same thing with JBoss 2.4.7
 + Tomcat (Catalina) 4.0.4 and it doesn't work at all !!

It appears to be deployed - the log file indicates that it is creating a module of <dir_name>/
with a context path of /<dir_name>/.  No errors on deployment.  Yet, when I try to hit a particular
.jsp immediately under that context path, say http://localhost/<dir_name>/<jsp_name> I get
a 500 error message from Catalina saying that there is no context configured to handle the
request.

I've tried putting the directory into JBoss' deploy directory.  I've tried putting the directory into
JBoss' deploy directory and then renaming it to <dir_name>.war, etc.  I get the same results
as above.  

The only time I can get it working with Tomcat is to package the directory up and deploy it
as a packaged file.  This ought to work!  Can anyone explain why it isn't?

rp

Reply via email to