« Return to Thread: mule 2.0/final: CXF and typeMappingRegistry

Re: mule 2.0/final: CXF and typeMappingRegistry

by ejoch :: Rate this Message:

Reply to Author | View in Thread

Fixed a Jira here:
http://mule.mulesource.org/jira/browse/MFPC-185

The Jira field options were a bit confusing- I wouldn't usually expect a field called 'project name' when submitting a bug! Hope it's gone into the correct place.

CXF documentation's suggested workaround for this hasn't changed since XFire - but that workaround assumes you can get to the bindings, which with the CXFReceiver methods being protected, you can't. So the override of typemappingregistry was a good solution- I *think* this property doesn't exist at all in 2.0.0, possibly because the CXF class formerly being overriden is now final?

perhaps I shall stick with XFire once it's available again.... I can't use the wsdls if they've got mandatory parameters exposed as non-mandatory.

 « Return to Thread: mule 2.0/final: CXF and typeMappingRegistry