-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Consistent compatibility with Woodstox as an alternative to Xerces #36682
Copy link
Copy link
Closed
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: enhancementA general enhancementA general enhancement
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
in: coreIssues in core modules (aop, beans, core, context, expression)Issues in core modules (aop, beans, core, context, expression)in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: enhancementA general enhancementA general enhancement
In various parts of the Spring codebase where we interact through JAXP, there are ties to the Xerces implementation as available from Apache and as shipped with the JDK. In addition to serving as a StAX provider, Woodstox also provides an alternative SAX implementation which can be manually configured on the user side. We should aim to officially support a user-configured Woodstox SAX setup as an alternative to Xerces, not least of it all for performance reasons.