Handle UnsupportedOperationException when creating XSDVALIDATING. #94

Merged
merged 1 commit into from Sep 27, 2012

Conversation

Projects
None yet
2 participants
@stefanbirkner
Contributor

stefanbirkner commented Sep 27, 2012

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.

Handle UnsupportedOperationException when creating XSDVALIDATING.
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

Merge pull request #94 from stefanbirkner/oldxerces
Handle UnsupportedOperationException when creating XSDVALIDATING.

@rolfl rolfl merged commit 804eb7b into hunterhacker:master Sep 27, 2012

@rolfl

This comment has been minimized.

Show comment
Hide comment
@rolfl

rolfl Sep 27, 2012

Collaborator

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

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

This comment has been minimized.

Show comment
Hide comment
@rolfl

rolfl Sep 27, 2012

Collaborator

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.

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

This comment has been minimized.

Show comment
Hide comment
@rolfl

rolfl Sep 27, 2012

Collaborator

Crap, put the wrong issue number on that commit.

Collaborator

rolfl commented Sep 27, 2012

Crap, put the wrong issue number on that commit.

@rolfl

This comment has been minimized.

Show comment
Hide comment
@rolfl

rolfl Sep 28, 2012

Collaborator

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

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

This comment has been minimized.

Show comment
Hide comment
@stefanbirkner

stefanbirkner Oct 1, 2012

Contributor

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

Contributor

stefanbirkner commented Oct 1, 2012

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