Create a subdirectory in your deploy directory called Context.war, replacing Context with whatever you want your web application context to be - for example MyApplication.war would create a context called MyApplication.
Under this subdirectory, unpack your WAR so it has the proper WAR directory structure e.g. WEB-INF with a web.xml file, lib and class directories and so forth.
Whenever you make a change by placing a new file in this unpacked WAR directory, touch the web.xml (update the date and timestamp on the file) and JBoss will redploy your web application.
tomcat41-service.xml no longer exists - it has been replaced by jboss-service.xml in the META-INF of the jbossweb-tomcat.sar. This unifies the view of the servlet container configuration, as it is the same for Jetty now. It just makes things less confusing.
Contexts don't really work as JBoss is handling deployment in a manner of speaking.
Thanks for your help, I finally get tomcat examples to
As you mentioned 'Context' deployment in this case is
handled by JBoss, I can't help wondering wher should
those 'context attributes' go. As tomcat 4.1.24 disabled symlinked webapps by default, we deploy
our web apps like below to enable symlinnking.
How should we do this in JBoss-tomcat bundle?
Check your server/instance/conf/jboss-service.xml file. You can specify other directories to scan for deployment. Look for details just above these lines:
Since you are not doing anything special with static resources, this configuration should meet your needs.