I knew that shortly after sending the email I'd get it sorted out. I needed to specify the wsdlLocation and list the serviceName and endpointName attributes, referenced by the namespace from the WSDL.
On Fri, May 15, 2009 at 2:26 AM, Nick Heudecker <[email protected]>wrote: > This one has me stumped. Here's what my Spring config looks like, with > some anonymized class names: > > <jaxws:endpoint id="foo" address="/foo" implementor="#fooService" > implementorClass="com.example.FooServiceImpl"> > <jaxws:dataBinding> > <ref bean="jaxbDataBinding"/> > </jaxws:dataBinding> > </jaxws:endpoint> > <jaxws:endpoint id="bar" address="/bar" implementor="#barService" > implementorClass="com.example.BarServiceImpl"> > <jaxws:dataBinding> > <ref bean="jaxbDataBinding"/> > </jaxws:dataBinding> > </jaxws:endpoint> > > With "bar" listed second, I get the following exception: > > Caused by: org.apache.cxf.service.factory.ServiceConstructionException: > Service class com.example.BarServer method serviceStatusNotification part { > http://www.scte.org/schemas/130-4/2008a/cis}request<http://www.scte.org/schemas/130-4/2008a/cis%7Drequest>cannot > be mapped to schema. Check for use of a JAX-WS-specific type without > the JAX-WS service factory bean. > > The "serviceStatusNotification" method is the first method listed in the > class. If I swap the config and list foo second, I get the exact same error > for the first method name in the FooService interface. > > No idea what's causing this. I'm on CXF 2.2.1. Any help is appreciated. > > Thanks for your time. > > -Nick >
