Hi Daniele,
VirtualHost should be defined per bundle/webapp, like we do for ContextPath.
It means that we should be able to define the VirtualHost in a way to be read
by Pax-Web to bind the jetty, something like:
<Configure class="org.eclipse.jetty.webapp.WebAppContext">
<Set name="contextPath">/xxx</Set>
<Set name="war"><SystemProperty name="jetty.home"/>/webapps/xxx.war</Set>
<Set name="virtualHosts">
<Array type="java.lang.String">
<Item>333.444.555.666</Item>
<Item>127.0.0.1</Item>
<Item>www.blah.com</Item>
<Item>www.blah.net</Item>
<Item>www.blah.org</Item>
</Array>
</Set>
</Configure>
I have to check that we can define it in the jetty.xml that you can put into
Karaf.
Regards
JB
On Fri 24/06/11 12:37 , Daniele Dellafiore wrote::
Hi.
After discovering the wonder of managed configuration in Karaf I'd
like to manage virtual hosts the same way with Pax Web + Jetty.
I wonder if this is possible. I do not think that my karaf is using
the etc/jetty.xml file now, while the properties in ops4j.pax.web.cfg
are.
How can I obtain the same results as
http://docs.codehaus.org/display/JETTY/Virtual+hosts
In a fashioned Karaf way?
I've found this doc
http://ops4j1.jira.com/wiki/display/paxweb/Advanced+Jetty+Configuration
Which could be a start.
Thanks.
--
Daniele Dellafiore
http://danieledellafiore.net
