I just located this issue:
Minimize CXF JAX-RS bundle
https://issues.apache.org/jira/browse/CXF-2269
Should it be updated to reflect your changes?
-- Robert
On Mon, Feb 7, 2011 at 8:41 PM, Sergey Beryozkin
<sberyoz...@gmail.com>wrote:
Hi
CXF JAX-RS depends on cxf-api, cxf-rt-core, cxf-common,
cxf-rt-transports-http and the xml binding.
cxf-rt-transports-http-jetty is still required in some cases - JIRA is
open;
cxf-api has some WSDL-related interfaces and thus a wsdl4j dependency is
still needed - two JIRAs are opened - one is to eliminate this dependency
Given that it must've been the 10th time I said we'd drop the wsdl4j
dependency :-) I just went ahead and applied the local changes I had
on my
laptop for a month, with a minor change. This was probably the most
complex
update, others will be much simpler
Cheers, Sergey
and another one is to exclude the WSDL-related and WS-Policy related api
from the final jar.
Overall no SOAP dependencies are required at all, only some of WS-* related
api is inherited - but we will make sure it's all minimized...
Cheers, Sergey
On Mon, Feb 7, 2011 at 6:23 PM, Benson Margulies <bimargul...@gmail.com>wrote
It is split. You can deploy just the jars you need.
On Mon, Feb 7, 2011 at 12:53 PM, robert <rob...@gliesian.com> wrote:
> This thread
> (
http://stackoverflow.com/questions/2704700/java-rest-implementation-jersey-vs-cxf
)
> states, "CXF is packaged up with SOAP stack support so you bring in a
lot of
> SOAP-related weight you'll never use when you build a RESTful system.
(There
> are plans to split the packaging as far as I know, though)".
>
> Are there plans to split the packaging? ... or did the user mean the
> opposite of what he said?
>
> Thanks!
>
>
