Class XMLValidationErrorHandler
java.lang.Object
com.compomics.util.pride.validation.XMLValidationErrorHandler
- All Implemented Interfaces:
ErrorHandler
Edited using IntelliJ IDEA Date: 16-Sep-2005 Time: 15:26:12
- Author:
- Phil Jones
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoiderror(SAXParseException exception) Receive notification of a recoverable error.voidfatalError(IOException exception) This is a extension method to the #fatalError(SAXParseException) method to allow the handling of IOExceptions.voidfatalError(SAXParseException exception) Receive notification of a non-recoverable error.Returns the errors as a list.Returns the errors formatted as HTML.Returns the errors formatted as plain text.booleannoErrors()Returns true of there were no errors.voidwarning(SAXParseException exception) Receive notification of a warning.
-
Constructor Details
-
XMLValidationErrorHandler
public XMLValidationErrorHandler()Constructor.
-
-
Method Details
-
noErrors
public boolean noErrors()Returns true of there were no errors.- Returns:
- true of there were no errors
-
getErrorsFormattedAsPlainText
Returns the errors formatted as plain text.- Returns:
- the errors formatted as plain text
-
getErrorsFormattedAsHTML
Returns the errors formatted as HTML.- Returns:
- the errors formatted as HTML
-
getErrorsAsList
Returns the errors as a list.- Returns:
- the errors as a list
-
error
Receive notification of a recoverable error.
This corresponds to the definition of "error" in section 1.2 of the W3C XML 1.0 Recommendation. For example, a validating parser would use this callback to report the violation of a validity constraint. The default behavior is to take no action.
The SAX parser must continue to provide normal parsing events after invoking this method: it should still be possible for the application to process the document through to the end. If the application cannot do so, then the parser should report a fatal error even if the XML 1.0 recommendation does not require it to do so.
Filters may use this method to report other, non-XML errors as well.- Specified by:
errorin interfaceErrorHandler- Parameters:
exception- The error information encapsulated in a SAX parse exception.- Throws:
SAXException- Any SAX exception, possibly wrapping another exception.- See Also:
-
fatalError
Receive notification of a non-recoverable error.
This corresponds to the definition of "fatal error" in section 1.2 of the W3C XML 1.0 Recommendation. For example, a parser would use this callback to report the violation of a well-formedness constraint.
The application must assume that the document is unusable after the parser has invoked this method, and should continue (if at all) only for the sake of collecting addition error messages: in fact, SAX parsers are free to stop reporting any other events once this method has been invoked.- Specified by:
fatalErrorin interfaceErrorHandler- Parameters:
exception- The error information encapsulated in a SAX parse exception.- Throws:
SAXException- Any SAX exception, possibly wrapping another exception.- See Also:
-
fatalError
This is a extension method to the #fatalError(SAXParseException) method to allow the handling of IOExceptions. Example: An FileNotFoundException is thrown by the validate method if the file to be validated contains a local reference to a DTD (which can not be found on the server).- Parameters:
exception- the IOException
-
warning
Receive notification of a warning.
SAX parsers will use this method to report conditions that are not errors or fatal errors as defined by the XML 1.0 recommendation. The default behavior is to take no action.
The SAX parser must continue to provide normal parsing events after invoking this method: it should still be possible for the application to process the document through to the end.
Filters may use this method to report other, non-XML warnings as well.- Specified by:
warningin interfaceErrorHandler- Parameters:
exception- The warning information encapsulated in a SAX parse exception.- Throws:
SAXException- Any SAX exception, possibly wrapping another exception.- See Also:
-