Deploy Tomcat application as ROOT contexto.
Now you can deploy a java application as any context (/foo, /foo2, ...) but it would be perfect to allow the deploy as ROOT (/).
Sorry, but we are dropped out support of java and Tomcat technology in the latest versions of Plesk due to low demand and resource intensity of development.
Numa Schmeder commented
When do you plan adding the feature ?
Another useful feature for java app is to allow them to be uploaded by ssh or ftp, some apps are 50Megs, and web upload doesn't seem adapted for big wars.
It would be nice to have a directory in plesk vhost called webapps or tomcat-apps where you can put your file in there and they will be deployed by tomcat auto deploy. Plesk should pick them up in the admin automatically
w. Popp commented
Install ROOT.war and patch the generated httpd.conf:
JkMount / ajp13
JkMount /* ajp13
(Better to use vhost.conf, but I didnt solve this yet)
Chris Becker commented
I want to give some further information: Normally when you develop a new web application, you want to deploy it under www.example.com
Under Plesk you don't have that possibility. The reason is, that tomcat creates the mapping out of the filename of the uploaded java-container. Those containers are *.war-files. In the case you upload sample.war, Plesk creates the corresponding mapping www.example.com/sample
But because [nothing].war is no valid filename there has to be a special case for those "root"-files. Tomcat documentation says, that these file have to be names ROOT.war in this case, tomcat knows, that it should deploy it under www.example.com:8080 but Plesk maps it to www.example.com/ROOT which in this single case is wrong. The solution for this bug is, that the Tomcat-Plesk-Addon simply checks for the one single special case filename=="ROOT.war" and handles the creation of the apache httpd - mapping accordingly.
The documentation of tomcat, where this special case is also descibed, can be found under: http://tomcat.apache.org/tomcat-7.0-doc/virtual-hosting-howto.html#General
I think it is really important to solve this as fast as possible, because in my opinion this special case is the case, that almost every tomcat plesk user is in. Thank you very much.