SAXException and make it an unchecked exception.
Xerces XNI doesn't allow SAXException to be thrown.
So when the user-supplied error handler throws it,
it needs to be tunneled through Xerces.
It is a bug if this exception "leaks" to the application. FIXME: use XNIException for this purpose. It's already doing this kind of SAXException tunneling.
| Modifier and Type | Field and Description |
|---|---|
| public final SAXException | |
| private static final long |
| Access | Constructor and Description |
|---|---|
| pack-priv |
| exception | back to summary |
|---|---|
| public final SAXException exception | |
| serialVersionUID | back to summary |
|---|---|
| private static final long serialVersionUID | |
| WrappedSAXException | back to summary |
|---|---|
| pack-priv WrappedSAXException(SAXException e) | |