Skip to content

TransformerFactoryUtils introduced in release 3.0.6 sets default properties that conflict with other TransformerFactory implementations [SWS-1054] #1120

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

Closed
gregturn opened this issue Feb 21, 2019 · 2 comments
Labels
status: duplicate A duplicate of another issue

Comments

@gregturn
Copy link
Contributor

gregturn commented Feb 21, 2019

Geert Graat opened SWS-1054 and commented

We recently upgraded to Spring WS 3.0.6. In this release, a new class is introduced, TransformerFactoryUtils (1f05307), which before instantiating a TransformerFactory sets some defaults. 

The problem we have with this is that we do not use the default TransformerFactory implementation, but instead rely on the Saxon-HE library. When this TransformerFactory is instantiated, setting the defaults lead to an exception:

 

Caused by: java.lang.IllegalArgumentException: Unrecognized configuration feature: http://javax.xml.XMLConstants/property/accessExternalDTDCaused by: java.lang.IllegalArgumentException: Unrecognized configuration feature: http://javax.xml.XMLConstants/property/accessExternalDTD at deployment.runtime.war//net.sf.saxon.Configuration.setConfigurationProperty(Configuration.java:4408) at deployment.runtime.war//net.sf.saxon.jaxp.SaxonTransformerFactory.setAttribute(SaxonTransformerFactory.java:311) at deployment.runtime.war//org.springframework.xml.transform.TransformerFactoryUtils.defaultSettings(TransformerFactoryUtils.java:53) at deployment.runtime.war//org.springframework.xml.transform.TransformerFactoryUtils.newInstance(TransformerFactoryUtils.java:32)

This prevents our application from starting up.

 


Affects: 3.0.6

@gregturn
Copy link
Contributor Author

Geert Graat commented

Ok, I see this has already been reported and fixed in #129. When can we expect a 3.0.7 release?

@gregturn gregturn added the status: waiting-for-triage An issue we've not yet triaged label Sep 22, 2020
@gregturn
Copy link
Contributor Author

@snicoll snicoll added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants