Skip to content

Handle UnsupportedOperationException when creating XSDVALIDATING. #94

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

Merged
merged 1 commit into from
Sep 27, 2012

Conversation

stefanbirkner
Copy link
Contributor

The SAXParserFactory throws an UnsupportedOperationException when setSchema
is called. Therefore every factory throws this exception unless it overrides
setSchema. A popular example is Apache Xerces SAXParserFactoryImpl before
version 2.7.0.

The SAXParserFactory throws an UnsupportedOperationException when setSchema
is called. Therefore every factory throws this exception unless it overrides
setSchema. A popular example is Apache Xerces SAXParserFactoryImpl before
version 2.7.0.
rolfl added a commit that referenced this pull request Sep 27, 2012
Handle UnsupportedOperationException when creating XSDVALIDATING.
@rolfl rolfl merged commit 804eb7b into hunterhacker:master Sep 27, 2012
@rolfl
Copy link
Collaborator

rolfl commented Sep 27, 2012

Makes sense. Can you comment on the rest of the functionality with 'old' xerces versions...? Is everything else working out OK?

@rolfl
Copy link
Collaborator

rolfl commented Sep 27, 2012

Just looking at the code, I think it would be useful to 'preserve' the actual exception, so that the original exception can be identified. I am going to tweak that area of code a little.

rolfl added a commit that referenced this pull request Sep 27, 2012
@rolfl
Copy link
Collaborator

rolfl commented Sep 27, 2012

Crap, put the wrong issue number on that commit.

@rolfl
Copy link
Collaborator

rolfl commented Sep 28, 2012

Hi Stefan.
Normally I would build a 'hotfix' package including this fix, and then post it to the jdom downloads page. In this case through, I have a bunch of un-committed dev code in my environment, and I would rather wait a bit. On the other hand, if you would find a quasi-official jdom-2.x-issues93through95.zip useful then I can arrange it. I will assume not unless you tell me otherwise.

Rolf

@stefanbirkner
Copy link
Contributor Author

I don't need a hotfix package very soon. I'm using another SAXParserFactory in the meantime: http://coderwall.com/p/kqsrrw

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.

2 participants