Would enabling schema validation do what you want? http://www.mail-archive.com/[EMAIL PROTECTED]/msg00125.html
It'll incur a bit of a performance hit but it should ensure that any types deviating from the WSDL (or referenced XSD) cause an error to be thrown. Andrew. 2008/9/24 samuel_rg <[EMAIL PROTECTED]>: > > I am deploying a Web Service using CXF 2.x. CXF 2.x internally uses JAXB > (2.x). When a soap message is received, if the JAXB unmarshalling comes up > with an error because of incorrect data (e.g. a String is passed instead of > an Integer) the default JAXB ValidationEventHandler does not throw a Fault > as it is configured to throw a Fault for SEVERE_ERROR only. > > And also in my server-side code in my method implemention the INteger that I > am expecting comes up as null and there is no way of me knowing that the > Client sent me incorrect value i.e. a String for an Integer as null could be > a valid value too if it is anoptional field. > > Is there any way in which I can override the default ValidationEventHandler > that comes with jaxb2.x or is there some other way to handle this issue. > > Regards > Samuel R > Senior J2EE Developer > TSYS Prepaid Systems > -- > View this message in context: > http://www.nabble.com/CXF-not-propagating-error-tp19659348p19659348.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
