-
Notifications
You must be signed in to change notification settings - Fork 1.1k
XPathMessageSplitter Not supported: http://javax.xml.XMLConstants/property/accessExternalDTD #2993
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
Comments
There appears to be a fix for this in 3.0.7 of spring-ws TransformerFactoryUtils but not the 2.4 line |
OK. Since there is not going to be a fix in Spring WS 2.4.x, I'm going to go ahead and cover all the |
This is one more concern from community about unstable Meanwhile I just copy/paste your class from the Thanks |
Fixes spring-projects#2993 Not all XML components support all the configuration properties. For example Saxon HE doesn't support `XMLConstants.ACCESS_EXTERNAL_DTD` and end up with an exception like: `IllegalArgumentException: Unknown configuration property http://javax.xml.XMLConstants/property/accessExternalDTD` * Copy `TransformerFactoryUtils` from the latest Spring WS, where all the attributes are wrapped into `try..catch` and warn log. And use this new class everywhere instead of non-patched in Spring WS * Upgrade to the latest Spring WS 2.4.5
Fixes #2993 Not all XML components support all the configuration properties. For example Saxon HE doesn't support `XMLConstants.ACCESS_EXTERNAL_DTD` and end up with an exception like: `IllegalArgumentException: Unknown configuration property http://javax.xml.XMLConstants/property/accessExternalDTD` * Copy `TransformerFactoryUtils` from the latest Spring WS, where all the attributes are wrapped into `try..catch` and warn log. And use this new class everywhere instead of non-patched in Spring WS * Upgrade to the latest Spring WS 2.4.5
Fixed via: #2994 |
Affects Version(s):4.3.20.RELEASE
Same issue as #2723 but using XPathMessageSplitter.
The text was updated successfully, but these errors were encountered: