Static Public Member Functions | |
String | checkElementName (String name) |
String | checkAttributeName (String name) |
String | checkCharacterData (String text) |
String | checkCDATASection (String data) |
String | checkNamespacePrefix (String prefix) |
String | checkNamespaceURI (String uri) |
String | checkNamespaceCollision (Namespace namespace, Namespace other) |
String | checkNamespaceCollision (Attribute attribute, Element element) |
String | checkNamespaceCollision (Namespace namespace, Element element) |
String | checkNamespaceCollision (Namespace namespace, Attribute attribute) |
String | checkNamespaceCollision (Namespace namespace, List list) |
String | checkProcessingInstructionTarget (String target) |
String | checkProcessingInstructionData (String data) |
String | checkCommentData (String data) |
String | checkPublicID (String publicID) |
String | checkSystemLiteral (String systemLiteral) |
String | checkXMLName (String name) |
boolean | isXMLCharacter (char c) |
boolean | isXMLNameCharacter (char c) |
boolean | isXMLNameStartCharacter (char c) |
boolean | isXMLLetterOrDigit (char c) |
boolean | isXMLLetter (char c) |
boolean | isXMLCombiningChar (char c) |
boolean | isXMLExtender (char c) |
boolean | isXMLDigit (char c) |
Verifier
handles XML checks on names, data, and other verification tasks for JDOM. The class is final and may not be subclassed.
Elliotte Rusty Harold
Jason Hunter
Bradley S. Huffman
|
This will check the supplied name to see if it is legal for use as a JDOM
|
|
This will check the supplied data to see if it is legal for use as JDOM
|
|
This will check the supplied string to see if it only contains characters allowed by the XML 1.0 specification. The C0 controls (e.g. null, vertical tab, formfeed, etc.) are specifically excluded except for carriage return, linefeed, and the horizontal tab. Surrogates are also excluded. This method is useful for checking element content and attribute values. Note that characters like " and < are allowed in attribute values and element content. They will simply be escaped as " or < when the value is serialized.
|
|
This will check the supplied data to see if it is legal for use as JDOM
|
|
This will check the supplied name to see if it is legal for use as a JDOM
|
|
Check if a
|
|
Check if a
|
|
Check if a
|
|
Check if
|
|
Check if two namespaces collide.
|
|
This will check the supplied name to see if it is legal for use as a JDOM
|
|
This will check the supplied name to see if it is legal for use as a JDOM
|
|
This will check the supplied data to see if it is legal for use as
|
|
This will check the supplied data to see if it is legal for use as a JDOM
|
|
This will ensure that the data for a public identifier is legal.
|
|
This will ensure that the data for a system literal is legal.
|
|
This is a utility function for sharing the base process of checking any XML name.
|
|
This is a utility function for determining whether a specified character is a character according to production 2 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is a combining character according to production 87 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified Unicode character is a digit according to production 88 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is an extender according to production 88 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is a letter according to production 84 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is a letter or digit according to productions 84 and 88 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is a name character according to production 4 of the XML 1.0 specification.
|
|
This is a utility function for determining whether a specified character is a legal name start character according to production 5 of the XML 1.0 specification. This production does allow names to begin with colons which the Namespaces in XML Recommendation disallows.
|