camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Bind certain camel-cxf service to a specific HttpConnector
Date Thu, 31 Jan 2013 20:54:17 GMT
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... ;-)




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message