[jboss-jira] [JBoss JIRA] (WFLY-11285) [IBM JDK] JBoss Modules are unable to load default JAXP implementation into deployment when SchemaFactory provider is set to implementation unavailable to deployment

Michal Jurc created WFLY-11285: ---------------------------------- Summary: [IBM JDK] JBoss Modules are unable to load default JAXP implementation into deployment when SchemaFactory provider is set to implementation unavailable to deployment Key: WFLY-11285 URL: https://issues.jboss.org/browse/WFLY-11285 Project: WildFly Issue Type: Bug Components: MSC Affects Versions: 14.0.0.Final Reporter: Michal Jurc Assignee: Alessio Soldano As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: {code:java} Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) ... 102 more {code} It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)