On Mar 22, 2013, at 9:46 AM, Richard Senior <[email protected]> wrote:
> The wsdl is valid because the maven codegen tool produces the classes without > error? Not necessarily. There are a bunch of things we don't validate there. You can pass the -validate flag to wsdl2java which will do MORE validation than the default, but still doesn't validate everything. > The annotations I understand, but CXF appears to be trying to reflect upon > my spring injected business logic beans which are unrelated to the operation > of the service itself. How are you deploying the service? There is a way to specify the endpointInterface to use just that and not the actual implementation. (or fill in the endpointInterface attribute on the @WebService annotation) > So for example I'm using HttpCommons to create a client for an old jaxrpc > service, and CXF is complaining about the inner workings of HttpCommons.. > > Is there any way to mark a member variable on a bean such that CXF does not > try to reflect upon it? If it's on a JAXB bean, then @XmlTransient Dan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Schema-validation-errors-on-publish-top-level-elements-may-not-have-a-use-tp5724860p5725013.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
