Project

Profile

Help

Revision 07a3ff72

Added by Michael Kay 9 months ago

Javadoc fixes

View differences:

latest10/hej/net/sf/saxon/lib/ErrorReporter.java
7 7

  
8 8
package net.sf.saxon.lib;
9 9

  
10
import net.sf.saxon.s9api.StaticError;
10 11
import net.sf.saxon.s9api.XmlProcessingError;
11 12
import net.sf.saxon.trans.UncheckedXPathException;
12 13
import org.xml.sax.ErrorHandler;
......
41 42
     * returns true.</p>
42 43
     *
43 44
     * <p>The application can indicate to Saxon that the error should be considered fatal
44
     * by calling {@link XmlProcessingError#setFatal(String)}. The precise effect of marking
45
     * by calling {@link StaticError#setFatal(String)}. The precise effect of marking
45 46
     * an error as fatal is not defined, and may depend on the circumstances; in some cases
46 47
     * it may have no effect. If a dynamic error is marked as fatal then an attempt to
47 48
     * catch the error using a try/catch construct in XSLT or XQuery will generally be
latest10/hej/net/sf/saxon/lib/StandardErrorReporter.java
11 11
import net.sf.saxon.expr.Expression;
12 12
import net.sf.saxon.expr.XPathContext;
13 13
import net.sf.saxon.expr.parser.XPathParser;
14
import net.sf.saxon.s9api.HostLanguage;
15
import net.sf.saxon.s9api.Location;
16
import net.sf.saxon.s9api.QName;
17
import net.sf.saxon.s9api.XmlProcessingError;
14
import net.sf.saxon.s9api.*;
18 15
import net.sf.saxon.trans.Err;
19 16
import net.sf.saxon.trans.XPathException;
20 17
import net.sf.saxon.trans.XmlProcessingException;
......
248 245
     *
249 246
     * <p>After calling this method to report a static error, the compiler will normally
250 247
     * continue to detect and report further errors, but the method can abort the
251
     * compilation by calling {@link XmlProcessingError#setFatal(String)}</p>
248
     * compilation by calling {@link StaticError#setFatal(String)}</p>
252 249
     *
253 250
     * @param error The error information.
254 251
     */

Also available in: Unified diff