[jboss-jira] [JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

[David Lloyd (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13650595#comment-13650595 ] 

David Lloyd commented on WFLY-11178:
------------------------------------

bq. The next question is - is it ok for the linked picketlink sources to set the system property? I guess we can't restrict users from doing so even in application code so jboss-modules should handle that somehow, right?

I'd say, no that's not OK, unless picketlink is also ensuring that the dependency is available.  Application code is certainly allowed to do so, but in that case it's up to them to ensure the dependency is added to the deployment.

> 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)