I have to use 3rd party Webservices that have many fields marked nillable="true" and minOccurs="0"
I am using CXF WSDL to java to generate java client classes with maven cxf-codegen-plugin 2.1.5 Because they are nillable CXF sends a perfectly legitimate nil value when there is no data for a field e.g. <ns2:TownCountry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true"/> But the 3rd party webservice cannot handle this. It is expecting no field. Is there anyway I can change my CXF client side to ignore nillable fields and not send them in the SOAP request if they are null? I've read these forums and haven't come up with a definitive answer. I was thinking using JAXB binding files to ignore the nillable aspect of the fields when the Java classes are created but JAXB binding is a black art to me. Any suggestions? Thanks Steve -- View this message in context: http://old.nabble.com/Ignoring-nillables-tp28159451p28159451.html Sent from the cxf-user mailing list archive at Nabble.com.
