Hi On Thu, Jan 6, 2011 at 3:32 PM, James Carr <[email protected]> wrote:
> Hi All, > > I'm currently investigating replacing some Jersey based services we > have with CXF and would like to know a couple questions. > > (1) Currently cxf-bundle-jaxrs brings in jetty, but our app isn't > going to run on jetty. Anyway to remove this dependency without > manually excluding it? > This is an optional dependency for the server side, it is there because quite a few CXF users use Jetty. It won't affect the applications deployed to other containers but I appreciate this a dependency which some/many developers may not want. We can definitely drop it but it is difficult to judge what is better/simpler : for users which do not need it to manually exclude it or for users who need it to manually add it. I do not know what percentage of CXF Maven users rely on Jetty and I guess it is simpler to exclude :-), so for a time being I'd prefer to keep that dependency. However, you may want the app to depend directly on cxf-rt-frontend-jaxrs and cxf-rt-transports-http, thus possibly avoiding having to explicitly exclude cxf-rt-transports-http-jetty. One dependency which is still required on the server side is wsdl4j - there's a CXF JIRA open to make sure it's made redundant. > (2) Is there a miminal jaxrs dependency that we can use in our clients? a > > The jetty dependency may still be (but not necessarily) required on the client side : https://issues.apache.org/jira/browse/CXF-3124 Depending on cxf-rt-frontend-jaxrs and cxf-rt-transports-http and few other cxf modules the above two dependencies will bring (cxf-api, cxf-common-utilities, etc) should do it. Spring deps are not strictly required Cheers, Sergey > Thanks, > James >
