Parser or write operations may throw an LSException if the
processing is stopped. The processing can be stopped due to a
DOMError with a severity of
DOMError.SEVERITY_FATAL_ERROR or a non recovered
DOMError.SEVERITY_ERROR, or if
DOMErrorHandler.handleError() returned false.
Note: As suggested in the definition of the constants in the
DOMError interface, a DOM implementation may choose to
continue after a fatal error, but the resulting DOM tree is then
implementation dependent.
Returns an array containing all of the exceptions that were
suppressed, typically by the try-with-resources
statement, in order to deliver this exception.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-07-10 UTC."],[],["`LSException`, a subclass of `RuntimeException`, is thrown when parsing or writing operations are halted. This halt can be due to a fatal `DOMError`, a non-recovered `DOMError`, or if `DOMErrorHandler.handleError()` returns `false`. The exception has two constants: `PARSE_ERR` (81) for parsing interruptions and `SERIALIZE_ERR` (82) for serialization interruptions. It also includes a public `code` field and a constructor to set the error `code` and message.\n"]]