[
https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-11178:
------------------------------------
If it is unspecified, it _should_ be using the default which we install at boot. This is
done by JBoss Modules, which adds a "virtual" service implementation to every
module that contains the "__redirected" class, which in turn calls the
implementation class. In this case, it will be the Xerces we bundle, even though it is
not actually on the deployment class path.
WSTrustTestCase failing on IBM
------------------------------
Key: WFLY-11178
URL:
https://issues.jboss.org/browse/WFLY-11178
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 14.0.0.Final
Reporter: Jan Blizňák
Assignee: Alessio Soldano
Priority: Major
Attachments: log.txt
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)