By default, the validation isn't even turned on. Thus nothing would get detected. You can turn the schema validation on and this should be caught and exception raised.
That said, with the latest 2.2 and 2.1 snapshots, there is a way to specify your own ValidationEventHandler in the config. I added that early last week. Dan On Wednesday 24 September 2008 6:25:03 pm samuel_rg wrote: > 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 -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
