I am upgrading my XFire web service logic to CXF 2.7.11 using simple frontend
due to annotation-less structure of course.
But CXF and XFire autogenerated namespaces (targetNamespace in wsdl) for web
services are different as CXF add an extra '/' forward slash. As mentioned
here
I think you have to move the XFireCompatibilityServiceConfiguration bean to
before the JaxWsServiceConfiguration. It’s a “first one to return a value
wins” thing so you need to make sure the XFire version gets a chance to return
the old xfire namespace before the JAX-WS algorithms kick in.
Tried already no luck.
On 2 Jun 2014 19:28, Daniel Kulp dk...@apache.org wrote:
I think you have to move the XFireCompatibilityServiceConfiguration bean
to before the JaxWsServiceConfiguration. It’s a “first one to return a
value wins” thing so you need to make sure the XFire version gets a
Thanks for taking interest Sir.
I tried
bean depends-on=scheduleService
class=com.resolution.scheduler.service.webservice.impl.WebServicesOptimiser
property name=serviceBean ref=scheduleService/property
/bean
And in method:
public void setServiceBean(Object serviceBean)
