The jetty transport will create a new jetty instance internally and listen on the specified port. It directly depends on jetty.
The servlet transport uses the OSGi HttpService. It only depends on the HttpService API. So to make it work you need to install a HttpService implementation. By default this is pax-web with the jetty backend. To use tomcat you need to install a HttpService based on Tomcat. I think pax-web might already provide this but I am not sure. Christian 2016-03-27 14:48 GMT+02:00 Setya <[email protected]>: > Hi Christian, > > Thank you for your hint. > > > As far as I can tell it only will work with the servlet transport. So > make > > sure you set an address like "/myservice". This will make CXF choose the > > servlet transport instead of the jetty transport. > > Could you please elaborate more on difference between servlet & jetty > transport ? > > > You will also need to > > make sure you have a HTTPService present that is backed by tomcat. > > In Karaf 4.0.3 I found only the following Tomcat related features: > > pax-http-tomcat > pax-war-tomcat > > Are they enough to accomplish the task ? > > Sorry, I'm pretty new to this stuff. > > Thanks & Regards, > Setya > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Combining-CXF-DOSGI-Tomcat-tp5765387p5767258.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- -- Christian Schneider http://www.liquid-reality.de <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de> Open Source Architect http://www.talend.com <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
