report over-long float and double as invalid in validateLexical

[aizu-m]

java.lang.IllegalArgumentException: Number has more than 1024 characters
    at org.apache.xmlbeans.impl.util.MathUtil.parseAsFloat(MathUtil.java:126)
    at org.apache.xmlbeans.impl.values.JavaFloatHolder.validateLexical(JavaFloatHolder.java:71)
    at org.apache.xmlbeans.impl.validator.Validator.validateAtomicType(Validator.java:1125)

Found this feeding long numeric text through validate(). A float or double literal longer than the XmlOptions maxNumberOfCharsForNumbers cap (1024 by default) reaches MathUtil.parseAsFloat/parseAsDouble, which enforce the cap by throwing IllegalArgumentException. validateLexical in JavaFloatHolder and JavaDoubleHolder only catches NumberFormatException, so the exception leaves doc.validate() instead of being recorded as an XmlError.

Two observations. validate() throws rather than returning false. And a union such as <xs:union memberTypes="xs:double xs:string"/> rejects a value that is valid against xs:string, because the validator probes the double member first and the exception escapes the member loop.

NumberFormatException is a subclass of IllegalArgumentException, so widening the catch keeps every existing invalid-lexical case and folds the length cap into a reported error. Regression test drives a 1025-char float and double through validate().

[pjfanning]

maybe we should catch RuntimeException or just generally not tie to one exact exception type