This is an example of schema validating with error feedback

Question

Hi,
Hope this is of help....
This is an example of schema validating WITH error feedback
public boolean validate(InputStream is) {
// create and setup the DOM parser object
parser = new DOMParser();
parser.setPreserveWhitespace(false);
parser.setValidationMode(XMLConstants.SCHEMA_STRICT_VALIDATION);
boolean isValid = false;
if (is != null) {
try {
parser.parse(new InputSource(is));
isValid = true;
} catch (XMLParseException e) {
for (int i = 0; i<e.getNumMessages() ;i++){
System.out.println("XMLParseException nr:"+new Integer(i+1)+" \'imsmanifest.xml\' line nr: "+new Integer(e.getLineNumber(i))+" col nr:"+
new Integer(e.getColumnNumber(i))+" (formatErrorMessage: "+e.formatErrorMessage(i)+") ["+e.getMessage(i)+"]");
} catch (java.io.IOException e) {
System.out.println("IOException: Error creating input source [" + e.getMessage() + "]");
} catch (org.xml.sax.SAXException e) {
System.out.println("SAXException: Error parsing [" + e.getMessage() + "]");
} catch (Exception e){
System.out.println("Exception: Error parsing [" + e.getMessage() + "]. ");
doc = parser.getDocument();
return isValid;
regards
Jon

Answer 1

"personally, I'd just put the exception handling into the package."
Maybe I am making this over-complicated. I would like all the error handling in the package. It seems like putting an ONSERVERERROR trigger would be a little overkill, and if it fires on every database error, and I have to screen for only my errors seems like a little overkill and to me, it seems like it would incur quite a bit of overhead for the database seeing it is firing for every error. I don't even know if I would ultimately be allowed to keep it.
Really, all I would want to do is:
1) Handle the error and recover if possible
2) If it is a fatal error, have a way to abort the package gracefully with some kind of record of it.
3) Allow for the possibility of non-fatal errors or messages, even that I might generate myself to be able to be logged.
This package has about 20 procedures now. If I have an error (particularly fatal), in let's say, procedure 8, I don't even know what happens. I don't know if by default it aborts the whole package or just that procedure or just keeps going. Is it possible to get just hung up and sit there?
Thanks for the input.