Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistent (SAX/DOM) wrapping of XML parse errors #482

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

jcflack
Copy link
Contributor

@jcflack jcflack commented Mar 31, 2024

The logic that chooses wrapping SQLException subclass and SQLstate for XML parse exceptions and I/O exceptions in XMLCopier.saxCopy is now duplicated in AdjustingDOMSource.get, to eliminate the inconsistency that an XML parse error would be reported as a class 22 SQLDataException if using the SAX or StAX APIs, but as a class XX internal-error SQLException if using the DOM API.

Addresses issue #481.

This does change a user-visible behavior. It would be straightforward to make it depend on a flag, if there exists any code depending on the prior behavior. (I am judging that unlikely.)

The logic that chooses wrapping SQLException subclass and SQLstate
for XML parse exceptions and I/O exceptions in XMLCopier.saxCopy
is now duplicated in AdjustingDOMSource.get.

Addresses issue #481.
@jcflack jcflack merged commit edc958b into REL1_6_STABLE Apr 3, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant