Hi, my blog is focused on WAR/WABs I'm gonna try to add some details on how to achieve this via the whiteboard extender. It's gonna take a bit :) If it's not possible now, I'm gonna add it for Pax-Web 3.0
regards, Achim 2013/1/31 Christian Müller <christian.muel...@gmail.com> > Some month ago I was looking for a way to bind camel-cxf to a specific > port, using the OSGI HTTP service. > Achim blogged about binding a web application to a specific port, using the > OSGI HTTP service and an adapted jetty.xml configuration [1]. I'm wondering > whether we can do the same with camel-cxf? > > The issue we face at present is, that all your services (service for > customer A, service for customer B, ...) are accessible on all ports. We > use specific ports for each customer, secured with client certificates to > make sure they only can access this port. But because all services are > exposed on all ports, this is useless... :-( > I know we can start an individual jetty for each service, but imagine we > have 10 different customer with individual applications. Each application > is composed of multiple bundles. Let's say 5 different bundles expose a web > service. This will end up starting 50 Jetty instances, right? Sounds very > inefficient and difficult to maintain for our operations people... > > Has an CXF expert time to look into it? I'm willing to sponsor a beer for > him/her - or two... ;-) > > [1] > > http://notizblog.nierbeck.de/2013/01/bind-certain-web-applications-to-specific-httpconnectors/ > > Best, > Christian > > -- > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
