I have an Embedded Customer that came up with a pretty cool "roll your own"
auto-deploy solution. He monitors 2 different directories.
In one of the directories he drops regular apps that get deployed to a
In the other one he drops apps that get deployed to a different https/virtual server
From what I've figured out from looking at the code in deployment/autodeploy and
examining domain.xml is that
1. Autodeploy can fairly easily be modified to have multiple instances
monitoring different directories
2. Autodeploy's granularity is at a sever-config level currently.
Allow AutoDeploy attributes inside http-service config as well as server-config.
Then the user can easily setup auto-deploy directories at a Virtual-server
granularity and do what my customer did just by making a few changes to the config.