There is a parameter you can define to prevent this very thing. <jaxws:properties> <entry key="jaxb.scanPackages" value="false" /> </jaxws:properties>
See here for an example: https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/resources/META-INF/scanPackagesContext.xml Sent from my Android phone On 12/10/2013 1:25 AM, "Aaron Titus" <ati...@fwdco.com> wrote: > I am using CXF 2.7.6 and deploying bottom-up web service, using jax-ws > annotated classes. I have a half a dozen web services, with 1 to 6 > operations each. I noticed that when viewing the WSDL for any one of the > services, that it always includes the type definitions for EVERY entity > class in the package, even the ones which are never referenced by the > specific service. > > Is there any option to prevent this? In my situation it makes the WSDL very > large, and it also adds confusion to the developers who are the consumers > of the service -- most of them will be inexperienced with web services. > > Thanks, > Aaron >
