Yeah, the issue is that jetty.xml in Karaf is "global" to the Jetty container.
Currently, the easiest way is to provide the VirtualHosts to the webapp as we do for ContextPath. I'm gonna enhance Pax-Web to support it. I raised KARAF-687 to track this. Regards JB On Fri 24/06/11 12:49 , Daniele Dellafiore wrote:: Yes the problem is that normally I have a special mywebapp.xml file like that in the /context folder in jetty. Here's there nos such thing, so I do not know what to do. On Fri, Jun 24, 2011 at 12:45 PM, Jean-Baptiste Onofré [email protected]> wrote: > 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: > > > /xxx > /webapps/xxx.war > > > 333.444.555.666 > 127.0.0.1 > www.blah.com > www.blah.net > www.blah.org > > > > > 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> > > > > -- Daniele Dellafiore http://danieledellafiore.net
