October 2018 - jboss-jira - Jboss List Archives

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

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-11178: ------------------------------------ [~jbliznak] do you have the rest of the stack trace? > 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 > > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3072) kie-maven-plugin to persist DMN Compilation results in KJAR like for DRL exec model rules

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3072?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3072: --------------------------------- Sprint: 2018 Week 42-44 > kie-maven-plugin to persist DMN Compilation results in KJAR like for DRL exec model rules > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3072 > URL: https://issues.jboss.org/browse/DROOLS-3072 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3112) FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper

by Tibor Zimányi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3112?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-3112: ---------------------------------- Story Points: 3 > FEEL Compiler: modularize FEELImpl compiler/interpreter vs. DMNFEELHelper > -------------------------------------------------------------------------- > > Key: DROOLS-3112 > URL: https://issues.jboss.org/browse/DROOLS-3112 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Code in FEELImpl could be reused in the DMNFEELHelper, but it cannot be shared, because FEELImpl exposes an interface to evaluate expressions, while DMNFEELHelper needs access to the compiler backend. > Solution: separate the compilation pipeline and the interpreter pipeline from the public FEEL interface to promote code reuse. In particular, CompilerBytecodeLoader can be probably split between some kind of CompiledUnit+CompiledUnaryTest impls that provide methods to retrieve Java source code and/or JVM bytecode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

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

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-11178: ------------------------------------ [~dmlloyd] this might need your attention as well, it might be only dependency loading issue after breaking change. > 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 > > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10336) MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood.

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-10336?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-10336: ------------------------------------ [~rsvoboda] I did an analysis of this some time ago but then was redirected to other tasks. I created a WFLY-11178 for that issue. Now, looking at what [~pmackay] posted, the root cause might be actually the same for both jiras. > MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood. > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10336 > URL: https://issues.jboss.org/browse/WFLY-10336 > Project: WildFly > Issue Type: Bug > Components: Test Suite, Web Services > Environment: {noformat} > Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled) > OpenJ9 - 49fcaf39 > OMR - 5cbbadf > IBM - 4453dac) > JCL - 20180319_01 based on Oracle jdk8u161-b12 > {noformat} > Reporter: Petr Kremensky > Assignee: Daniel Čihák > Priority: Major > > There are test failures running the WildFly Test Suite: Integration - WS on IBM jdk. > {noformat} > wildfly/testsuite/integration/ws] $ mvn clean install > ... > [INFO] > [INFO] Results: > [INFO] > [ERROR] Errors: > [ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://... > [ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc... > [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault > [ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault > [ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand... > [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault > [ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault > [ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he... > [ERROR] WSTrustTestCase.test:318 » SOAPFault MustUnderstand headers: [{http://docs.oas... > [ERROR] WSTrustTestCase.testActAs:441 » SOAPFault MustUnderstand headers: [{http://doc... > [ERROR] WSTrustTestCase.testBearer:541 » SOAPFault MustUnderstand headers: [{http://do... > [ERROR] WSTrustTestCase.testHolderOfKey:491 » SOAPFault MustUnderstand headers: [{http... > [ERROR] WSTrustTestCase.testNoClientCallback:383 » SOAPFault MustUnderstand headers: [... > [ERROR] WSTrustTestCase.testNoSignatureUsername:414 » SOAPFault MustUnderstand headers... > [ERROR] WSTrustTestCase.testOnBehalfOf:468 » SOAPFault MustUnderstand headers: [{http:... > [ERROR] WSTrustTestCase.testPicketLink:518 » SOAPFault MustUnderstand headers: [{http:... > [ERROR] WSTrustTestCase.testUsingEPR:350 » SOAPFault MustUnderstand headers: [{http://... > [INFO] > [ERROR] Tests run: 119, Failures: 0, Errors: 17, Skipped: 0 > {noformat} > *Caused by* > {noformat} > Caused by: org.apache.cxf.binding.soap.SoapFault: MustUnderstand headers: [{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security] are not understood. > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:87) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:53) > at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:42) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112) > at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:70) > at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:35) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:827) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1695) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1572) > at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1373) > at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56) > at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:673) > at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) > at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:533) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:442) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:343) > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296) > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96) > at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:139) > ... 129 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3135) Create Scenario Simulation Selenium test covering basic operations

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3135?page=com.atlassian.jira.plugi... ] Klara Kufova moved BAQE-558 to DROOLS-3135: ------------------------------------------- Project: Drools (was: Red Hat Business Automation Quality Engineering) Key: DROOLS-3135 (was: BAQE-558) Workflow: GIT Pull Request workflow (was: Software Simplified Workflow for Project BXMSQE) Docs QE Status: NEW QE Status: NEW > Create Scenario Simulation Selenium test covering basic operations > ------------------------------------------------------------------ > > Key: DROOLS-3135 > URL: https://issues.jboss.org/browse/DROOLS-3135 > Project: Drools > Issue Type: Task > Reporter: Klara Kufova > Assignee: Klara Kufova > Priority: Major > Labels: ScenarioSimulation > > Create a Scenario Simulation Selenium test that covers the following basic operations: > _Test create and open test scenario. Run Test and check the reporting panel has opened. Make changes, save, and reopen. Test copy, rename, and delete test scenario._ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2958) Write integration test for the scenario runner.

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-2958?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2958: --------------------------------- Sprint: (was: 2018 Week 42-44) > Write integration test for the scenario runner. > ----------------------------------------------- > > Key: DROOLS-2958 > URL: https://issues.jboss.org/browse/DROOLS-2958 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Juraj Soltes > Priority: Major > > Write tests that would call ScenarioRunner::run on realistic examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

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

by Jan Blizňák (Jira)

Jan Blizňák created WFLY-11178: ---------------------------------- Summary: 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 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2866) Docks used by editors are broken in embed enviroments

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-2866?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2866: --------------------------------- Sprint: (was: 2018 Week 45-47) > Docks used by editors are broken in embed enviroments > ----------------------------------------------------- > > Key: DROOLS-2866 > URL: https://issues.jboss.org/browse/DROOLS-2866 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Stunner > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam > > Any editor depending on the need of Docks needs a Perspective around it to have the Docks included. > This means the Appformer standalone editor perspective or any custom perspective that uses these screens does not show the Docks panel and the editor lacks editing features. > Areas hit by this issue: > * DMN Editor > * Data Modeller > * Scenario Simulation editor > * Case management editor > * BPMN Process editor > * Page authoring editor > * Form layout editor > * Manage section > Possible fixes: > * Add a dock for the editor > * Add a dock for appformer standalone perspective > Might be it is enough to add the dock for standalone perspective. This needs some investigation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2783) Add read only support to Scenario Simulation asset

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-2783?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-2783: --------------------------------- Sprint: (was: 2018 Week 45-47) > Add read only support to Scenario Simulation asset > -------------------------------------------------- > > Key: DROOLS-2783 > URL: https://issues.jboss.org/browse/DROOLS-2783 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > All the editors should be able to be opened in read only mode. > Add this feature to Scenario Simulation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018