… a singleton has failed to intialize
The SAXParserFactory throws an UnsupportedOperationException when setSchema is called. Therefore every factory throws this exception unless it overrides setSchema. A popular example is Apache Xerces SAXParserFactoryImpl before version 2.7.0.
The fix for this check results in some checks being done in a few places, and not all of these places were covered in the test-harness, resulting in uncovered code. This commit ensures that all places that check attributes now have appropriate test cases.
The code will now verify the second character in a name. Additionally, the error messages for broken names has been improved to indicate what both the broken name and character are, instead of just the character. Also, change the checkNamespacePrefix code to leverage the common code from checkElementName and checkAttributeName. Also improve the test harness to cover test cases that are now more complicated because the name-check code is in two places now instead of one....
…ct ensure even byte allocations.... what was I thinking.
… 'setting' an Attribute.
…s for SAX parsing. Also update the sax-based parsing descriptions/documentation.
…like custom subclasses of Element). Upgrade the serialiazion test-code to report exceptions better. Add a test-case that checks that all subclasses are serializable.
…ault namespace for XPath expression.
….z to jdom2-x.y.z with different maven artifact id's for JDOM 1.x and 2.x it is possible to have both jars in the same maven project.
…ve() This fix changes the tracking of dataModCount so that it is updated on remove(). Additionally, it centralizes the processing to b consistent with the size-mod-count (and data-mod-count).
…n heap space.
…xes a broken context in Android where the base directory is not populated correctly.
… is no accessible STDERR (or STDOUT). Instead 'chain' the problem.