List of fatalError() Examples

Examples of fatalError()

com.gargoylesoftware.htmlunit.DefaultCssErrorHandler.fatalError()
{@inheritDoc}
com.sun.org.apache.xerces.internal.xni.parser.XMLErrorHandler.fatalError()
Report a fatal error. Fatal errors usually occur when the document is not well-formed and signifies that the parser cannot continue normal operation.
Note: The error handler should always throw an XNIException from this method. This exception can either be the same exception that is passed as a parameter to the method or a new XNI exception object. If the registered error handler fails to throw an exception, the continuing operation of the parser is undetermined. @param domain The domain of the fatal error. The domain can beany string but is suggested to be a valid URI. The domain can be used to conveniently specify a web site location of the relevent specification or document pertaining to this fatal error. @param key The fatal error key. This key can be any stringand is implementation dependent. @param exception Exception. @throws XNIException Thrown to signal that the parser should stopparsing the document.
com.sun.tools.internal.ws.processor.modeler.wsdl.ConsoleErrorReporter.fatalError()
com.sun.tools.ws.processor.modeler.wsdl.ConsoleErrorReporter.fatalError()
com.volantis.xml.pipeline.sax.XMLProcess.fatalError()
hudson.util.StreamTaskListener.fatalError()
javax.xml.transform.ErrorListener.fatalError()

Receive notification of a non-recoverable error.

The Transformer must continue to try and provide normal transformation after invoking this method. It should still be possible for the application to process the document through to the end if no other errors are encountered, but there is no guarantee that the output will be useable.
@param exception The error information encapsulated in aTransformerException. @throws javax.xml.transform.TransformerException if the applicationchooses to discontinue the transformation. @see javax.xml.transform.TransformerException
mf.org.apache.xerces.xni.parser.XMLErrorHandler.fatalError()
Report a fatal error. Fatal errors usually occur when the document is not well-formed and signifies that the parser cannot continue normal operation.
Note: The error handler should always throw an XNIException from this method. This exception can either be the same exception that is passed as a parameter to the method or a new XNI exception object. If the registered error handler fails to throw an exception, the continuing operation of the parser is undetermined. @param domain The domain of the fatal error. The domain can be any string but is suggested to be a valid URI. The domain can be used to conveniently specify a web site location of the relevant specification or document pertaining to this fatal error. @param key The fatal error key. This key can be any string and is implementation dependent. @param exception Exception. @throws XNIException Thrown to signal that the parser should stopparsing the document.
org.apache.avalon.framework.logger.CommonsLogger.fatalError()
@see org.apache.avalon.framework.logger.Logger#fatalError(java.lang.String)
org.apache.avalon.framework.logger.Logger.fatalError()
Log a fatalError message. @param message the message
org.apache.hama.ipc.BSPPeerProtocol.fatalError()
Report that the task encounted a fatal error.
org.apache.log.Logger.fatalError()
Log a fatalError priority event. @param message the message @param throwable the throwable
org.apache.woden.ErrorHandler.fatalError()
org.apache.xerces.xni.parser.XMLErrorHandler.fatalError()
Report a fatal error. Fatal errors usually occur when the document is not well-formed and signifies that the parser cannot continue normal operation.
Note: The error handler should always throw an XNIException from this method. This exception can either be the same exception that is passed as a parameter to the method or a new XNI exception object. If the registered error handler fails to throw an exception, the continuing operation of the parser is undetermined. @param domain The domain of the fatal error. The domain can be any string but is suggested to be a valid URI. The domain can be used to conveniently specify a web site location of the relevent specification or document pertaining to this fatal error. @param key The fatal error key. This key can be any string and is implementation dependent. @param exception Exception. @throws XNIException Thrown to signal that the parser should stopparsing the document.
org.apache.xml.utils.DefaultErrorHandler.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.
@param exception The error information encapsulated in aSAX parse exception. @throws SAXException Any SAX exception, possiblywrapping another exception.
org.codehaus.dna.impl.SAXConfigurationHandler.fatalError()
Rethrow exception and dont attempt to do any error handling. @param spe the input exception @throws SAXException always thrown
org.codehaus.plexus.logging.Logger.fatalError()
org.objectweb.celtix.configuration.impl.TypeSchema.TypeSchemaErrorHandler.fatalError()
org.xml.sax.ErrorHandler.fatalError()
Receive notification of a non-recoverable error.
There is an apparent contradiction between the documentation for this method and the documentation for {@link org.xml.sax.ContentHandler#endDocument}. Until this ambiguity is resolved in a future major release, clients should make no assumptions about whether endDocument() will or will not be invoked when the parser has reported a fatalError() or thrown an exception.

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 additional error messages: in fact, SAX parsers are free to stop reporting any other events once this method has been invoked.
@param exception The error information encapsulated in aSAX parse exception. @exception org.xml.sax.SAXException Any SAX exception, possiblywrapping another exception. @see org.xml.sax.SAXParseException

Examples of org.objectweb.celtix.configuration.impl.TypeSchema.TypeSchemaErrorHandler.fatalError()

        } catch (SAXParseException ex) {
             // ignore;
        }
        
        try {
            eh.fatalError(spe);
            fail("Expected SAXParseException not thrown.");
        } catch (SAXParseException ex) {
             // ignore;
        }          
    }

View Full Code Here

Examples of org.xml.sax.ErrorHandler.fatalError()

        documentMediaType = matcherCTRL.replaceAll(EMPTY_STRING);
      }
      OdfValidationException ve = new OdfValidationException(OdfSchemaConstraint.DOCUMENT_WITHOUT_ODF_MIMETYPE,
          internalPath, documentMediaType);
      if (errorHandler != null) {
        errorHandler.fatalError(ve);
      }
      throw ve;
    }
    return newDocument(odfPackage, internalPath, odfMediaType);
  }

View Full Code Here

0 1 2 3 4 5 6

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.