report length facets in JavaNotationHolderEx.validateLexical

[aizu-m]

Spotted while comparing the two NOTATION validation paths against the anyURI ones. Setting a too-long value throws, but loading the same value from a document validates clean.

base NOTATION enumerates t:a and t:bcdefgh; a derived type adds maxLength=3
document value 't:bcdefgh' (length 9, still in the inherited enumeration)

before:  doc.validate() == true, no errors raised
after:   cvc-maxLength-valid.1.1  NOTATION length (9) is greater than maxLength facet (3)

validateLexical called check(v, sType) and dropped the boolean it returns, so the length, minLength and maxLength facets were never handed to the ValidationContext. check() is the same helper set_text uses, and that path does reject the value (PR #45). The enumeration check does not catch it because the value is a legitimate inherited enumeration member.

The anyURI sibling, JavaUriHolderEx.validateLexical, already reports these facets inline. This makes NOTATION report them the same way and leaves check() untouched for the set path.