On Tuesday 02 December 2008 6:50:00 am Ian Roberts wrote: > I can see why CXF has so many *compile-time* dependencies, but I think > the original question was more like how many of these dependencies are > actually required at run time if you're only doing simple stuff like a > single JAX-WS client that doesn't use WS-anything? Presumably this case > would only use a subset of the classes in each CXF module.
The JAX-WS TCK/Compliance statement that we have actually throws the biggest wrinkle in things. To claim compliance, the "out of the box"/"default" experience HAS to be completely compliant. Thus, anything that JAX-WS REQUIRES would have to be "runtime" scope dependencies, not "provided" or "optional". Thus, things like WS-Addressing, catalogs, etc.... would have to be full runtime deps. Thus, for JAX-WS stuff, it may really be a "documentation" exercise to state which deps you should be able to "exclude". -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
