org.apache.xerces.util
abstract public class: ErrorHandlerProxy [javadoc |
source]
java.lang.Object
org.apache.xerces.util.ErrorHandlerProxy
All Implemented Interfaces:
ErrorHandler
Wraps
XMLErrorHandler and make it look like a SAX
ErrorHandler .
The derived class should override the #getErrorHandler() method
so that it will return the correct XMLErrorHandler instance.
This method will be called whenever an error/warning is found.
Experience shows that it is better to store the actual
XMLErrorHandler in one place and looks up that variable,
rather than copying it into every component that needs an error handler
and update all of them whenever it is changed, IMO.
- author:
Kohsuke - Kawaguchi (kohsuke.kawaguchi@sun.com)
- version:
$ - Id: ErrorHandlerProxy.java 447241 2006-09-18 05:12:57Z mrglavas $
| Method from org.apache.xerces.util.ErrorHandlerProxy Detail: |
public void error(SAXParseException e) throws SAXException {
XMLErrorHandler eh = getErrorHandler();
if (eh instanceof ErrorHandlerWrapper) {
((ErrorHandlerWrapper)eh).fErrorHandler.error(e);
}
else {
eh.error("","",ErrorHandlerWrapper.createXMLParseException(e));
}
// if an XNIException is thrown, just let it go.
// REVISIT: is this OK? or should we try to wrap it into SAXException?
}
|
public void fatalError(SAXParseException e) throws SAXException {
XMLErrorHandler eh = getErrorHandler();
if (eh instanceof ErrorHandlerWrapper) {
((ErrorHandlerWrapper)eh).fErrorHandler.fatalError(e);
}
else {
eh.fatalError("","",ErrorHandlerWrapper.createXMLParseException(e));
}
}
|
abstract protected XMLErrorHandler getErrorHandler()
|
public void warning(SAXParseException e) throws SAXException {
XMLErrorHandler eh = getErrorHandler();
if (eh instanceof ErrorHandlerWrapper) {
((ErrorHandlerWrapper)eh).fErrorHandler.warning(e);
}
else {
eh.warning("","",ErrorHandlerWrapper.createXMLParseException(e));
}
}
|