Perfect! It would appear that we need to investigate our flex client then because it seems to be passing along valid NaNs for floats and doubles, but it's also passing them for integers and we'll need to figure that out.
Thanks for the help. Aaron On Thu, Feb 24, 2011 at 2:06 PM, Daniel Kulp <[email protected]> wrote: > On Thursday 24 February 2011 9:22:28 AM Aaron Ehrensberger wrote: > > Hi all, > > > > I'm hoping someone can help me out here... > > > > We recently upgraded CXF from 2.2.3 to 2.3.1. In doing so, it would > appear > > that some of our webservices have been broken in the process. > > > > Specifically, the issue we're having is that our client is passing across > a > > field like <integerValue>NaN</integerValue>, which previously was being > > processed fine and we didn't have issues. However, it would appear that > > now, we are throwing an UnmarshallingException. Debugging through > eclipse, > > we see an error like... > > DefaultValidationEventHandler: [ERROR]: Not a number: NaN > > Location: line 49 - that class comes from jaxb-api jar > > > > That said - any ideas what to look for or change? > > If it's an integer, than NaN is not a valid value and the exception is what > should be occuring. Ignoring that could have been considered a bug in > 2.2.3. > > That said, you can set a property of: > "set-jaxb-validation-event-handler" to "false" > on the endpoint and it would again be ignored. > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com > -- Aaron Ehrensberger Software Architect DocFinity® by Optical Image Technology, Inc. 100 Oakwood Avenue, State College, PA 16803 ph: 814.238.0038 ext. 270 fax: 814.238.0011 email: [email protected] web: www.docfinity.com
