There is a patch in the jboss patch list to do virtual host support.
It seems to take the route of adding a virtual host attribute to the
J2EEDeployer - one deployer:one host. So the more virtual hosts you
want, the more J2EEDeployers you run.
This is quite nice as it means you can do stuff like move an ear from
host1.deploy/foo.ear to host2.deploy/foo.ear and your app will be
hot-undeployed from one virtual host and hot-redeployed onto another
one.
I did kick off a thread about this a while ago, but I want to approach
this from a different angle and get a consensus on how it should be
done, since I think it would be fun to have.
1. Are virtual hosts an EAR or WAR level thang ? e.g. do they have any
relevance to EJBs ?
2. Is there any support for it in standard J2EE descriptors ?
3. If not, should it be configured in e.g. a proprietary descriptor, or
achieved in some other way (like multiple deployers) ?
I like the multiple deployer solution presented, however I see a couple
of problems.
If this is a WAR level abstraction, then you could argue that changes to
accomodate it should only impact on the web-container.
What happens if you want to say e.g. app1 runs on host1,2,3 and app2
runs on host2,3,4 ? You could do it by deploying multiple copies of the
apps, but I am sure i recall being shown a piece of configuration in
which a list of hosts was configured for a single app....
Perhaps a single deployer could support a group of virtual hosts ? - or
is this just multiple deployers watching a single directory (No, because
you may want to talk to a single deployer via e.g. JMX)_..
etc...
Anyone interested ?
Jules
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
