Hi Lars, I have found that the easiest approach to your issue is to use Camel as an HTTP/S proxy and locking Karaf's HTTP Service to local host. You gain greater flexibility and an additional filter layer if needed. Write it with CM service configuration support to add a dynamic producer driven by request path properties (/my/web/service becomes my.web.service=<internal host>).
Another alternative would be to us the Camel CXF Transport. I have found it to be the most fine grained of all options since you can expose your CXF Service using any type of transport on any port you like. Regards, Scott ES -- -- Scott England-Sullivan ---------------------------------- FuseSource Web: http://www.fusesource.com Blog: http://sully6768.blogspot.com Twitter: sully6768 On Thu, Jul 19, 2012 at 2:56 AM, helander <leh...@gmail.com> wrote: > I just realized from your description that CXF does not explicitly register > with the http services, but rely on the Pax Web Whiteboard extender to > perfom the registration. This means that it would not be possible to use a > service filter between CXF and the http service (the whiteboard extender > would also have to beware of this filter). I do not think that this is > something that PAX Web whiteboard supports. > > /Lars > > -- > View this message in context: > http://camel.465427.n5.nabble.com/cxfEndpoints-and-different-transports-http-https-using-PAX-Web-tp5716216p5716236.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
