Jetty supports virtual hosts. AFAIK, JBoss' deployment
mechanism currently does not.
You have two choices:
1. The JBoss/Jetty integration preserves Jetty's
proprietary configuration abilities. i.e. you could
configure your webapps to be deployed onto virtual
hosts via the jetty.xml file. The problem with this is
that you shortcut around all the integration code and
miss out on e.g. optimised inter-vm calls, ENC
support, JBossSX/JAAS integrations, hot-deployment
etc...
2. With a very small amount of hacking you could fix
the integration code to allow you to somehow specify a
virtual host for each webapp. The only reason that I
have not yet done this, is that I am waiting for JBoss
to implement a complete solution for virtual hosts
that I can integrate into, rather than just going my
own way. There was a ?patch? floating around for 2.?
that allowed you to run up a Deployer for each virtual
host. So you might have a deploy.host1, deploy.host2,
deploy.host3 etc... directories, and depending on
which one you drop your ear into.
Scott was considering the implications of this on the
rest of JBoss and was going to come to some
conclusion, but I guess JBoss3 came first.
Are you running 3.0 or 2.x. If 2.x building your own
JBoss/Jetty is slightly more complicated. If you plan
to do this, drop me a line and I will let you know
how.
There was one other way which I saw someone using, but
it was a real hack. Jetty will read a proprietary
descriptor for each webapp (?jetty-web.xml?) in which
you can access it's configuration API. I think someone
was using this to somehow register a new listener on a
virtual host for the webapp in question, but it was a
pretty nasty way of doing it.
Hope that helps,
Jules
--- rgibbs42 <[EMAIL PROTECTED]> wrote: > I have
been reading through the archives about
> virtual hosting and
> have looked at the documentation but still can't
> seem to figure out
> how to achieve what we need.
>
> Currently we are using resin but would like to
> switch over to jetty
> since most of our application is running in jboss.
> Through resin's
> apache module, we are able to define multiple
> virtual hosts each with
> their own docroot while sharing the same instance of
> resin which has
> one copy of our template engine running.
>
> Can you configure jetty to have the similar
> functionality?
>
> Thanks
>
>
>Rick
>
>
> Yahoo! Groups Sponsor
> -~-->
> Tiny Wireless Camera under $80!
> Order Now! FREE VCR Commander!
> Click Here - Only 1 Day Left!
>
http://us.click.yahoo.com/75YKVC/7.PDAA/ySSFAA/CefplB/TM
>
-~->
>
> For the latest information about Jetty, please see
> http://jetty.mortbay.
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
