June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5403) [Scesim Editor] Impossible to set collection element to null

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5403?page=com.atlassian.jira.plug... ] Anna Dupliak reassigned DROOLS-5403: ------------------------------------ Component/s: Scenario Simulation and Testing Tester: Anna Dupliak Description: If user tests collection of boolean/ enum /most of the complex type except String - that should contain a null value - it got a message: "The expected value is '[{"value":"null"}]' but the actual one is 'null'." If user follows the suggestion then he got unexpected error SEE: [^nullCollectionElement.webm] Steps to Reproduce: # Import [^MySpace_TestEnumTest2.zip] # Go to testSurnameEnding # Run test Expected: test passed Actual: test failing with "The expected value is '[{"value":"null"}]' but the actual one is 'null'." Attachment: MySpace_TestEnumTest2.zip nullCollectionElement.webm Affects Version/s: 7.39.0.Final Assignee: Yeser Amer (was: Mario Fusco) > [Scesim Editor] Impossible to set collection element to null > ------------------------------------------------------------ > > Key: DROOLS-5403 > URL: https://issues.redhat.com/browse/DROOLS-5403 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Attachments: MySpace_TestEnumTest2.zip, nullCollectionElement.webm > > > If user tests collection of boolean/ enum /most of the complex type except String - that should contain a null value - it got a message: > "The expected value is '[{"value":"null"}]' but the actual one is 'null'." > If user follows the suggestion then he got unexpected error SEE: [^nullCollectionElement.webm] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5403) [Scesim Editor] Impossible to set collection element to null

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-5403: ------------------------------------ Summary: [Scesim Editor] Impossible to set collection element to null Key: DROOLS-5403 URL: https://issues.redhat.com/browse/DROOLS-5403 Project: Drools Issue Type: Bug Reporter: Anna Dupliak Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1979: --------------------------------------- This will get interesting. Our build requires Java 11 as we have some multi module jars which allow us to use some later APIs to move away from some of the "workarounds" we needed when running against Java 8, as defined in jboss-parent we however still target Java 8: {code:xml} <maven.compiler.target>1.8</maven.compiler.target> <maven.compiler.source>1.8</maven.compiler.source> {code} We then redefine the maven-compiler-plugin and set the release version to 8: {code:xml} <release>8</release> {code} This parameter is passed straight to javac, According to the documentation for the release parameter: {quote} Compiles against the public, supported and documented API for a specific VM version. Supported release targets are 6, 7, 8, 9, 10, and 11. {quote} https://docs.oracle.com/en/java/javase/11/tools/javac.html It seems even the latest versions of Java 11 don't agree these new methods are part of the Java 8 API. If I remove the release setting the use of these new methods build cleanly but it does leave the project at risk of using API later than Java 8. I can probably relax this check just for the affected component to get the changes through but we may now need an alternative API check to double check we don't accidentally introduce anything else new - so far this configuration has been quite reliable at providing the protection we need. > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-998) Fix kiali_qe.tests.test_graph_page.test_filter

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-998?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan resolved SWSQE-998. ---------------------------------- Resolution: Done This issue is resolved. > Fix kiali_qe.tests.test_graph_page.test_filter > ---------------------------------------------- > > Key: SWSQE-998 > URL: https://issues.redhat.com/browse/SWSQE-998 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Priority: Major > Labels: automation > > This test is failing due to new PF 4 changes. > selenium.common.exceptions.NoSuchElementException: Message: Could not find an element '//[contains(@class, "pf-c-dropdown__menu")]//[contains(@class, "pf-c-dropdown__menu-item")]' -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1150) Overview - Idle status automation

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1150?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1150: ---------------------------------- Sprint: Kiali Sprint #40 > Overview - Idle status automation > --------------------------------- > > Key: SWSQE-1150 > URL: https://issues.redhat.com/browse/SWSQE-1150 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5374) PMML presentation

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5374?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5374. ------------------------------------ Resolution: Done Presentation done. Available documents: https://docs.google.com/document/d/1DsOKc66iWj0HTUgggTh3AoH9B6Sy1Si8cdvt8... https://docs.google.com/presentation/d/1LQ9bP_d4EwPsHb1q8WXOYxA4XJaC32S_P... https://drive.google.com/open?id=19wFr8L_naHQ15XM-rE2T23EWL9idJro1 > PMML presentation > ----------------- > > Key: DROOLS-5374 > URL: https://issues.redhat.com/browse/DROOLS-5374 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Write an introductory document about PMML standard - not too technical - general overview. > Prepare slides out of it. > Make a presentation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13554) Test Cases of JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13554?page=com.atlassian.jira.plugi... ] Parul Sharma updated WFLY-13554: -------------------------------- Description: Test case for this issue https://issues.redhat.com/browse/WFLY-13375, if connection factory or JMS destination is configured for third party resource adapter. (was: Test case for this issue https://issues.redhat.com/browse/WFLY-13375, if connection factory or JMS destination is configured for third party resource adapter #13241) > Test Cases of JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-13554 > URL: https://issues.redhat.com/browse/WFLY-13554 > Project: WildFly > Issue Type: Bug > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > > Test case for this issue https://issues.redhat.com/browse/WFLY-13375, if connection factory or JMS destination is configured for third party resource adapter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5360) Avoid direct invocation of PMMLModelExecutor.evaluate

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5360?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5360. ------------------------------------ > Avoid direct invocation of PMMLModelExecutor.evaluate > ----------------------------------------------------- > > Key: DROOLS-5360 > URL: https://issues.redhat.com/browse/DROOLS-5360 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > -Change PMMLModelExecutor public API so that user should not retrieve the KiePMMLModel to invoke the "evaluate" method- > -PMML4Result evaluate(final KieBase knowledgeBase, KiePMMLModel model, PMMLContext context)- > -> > -PMML4Result evaluate(final KieBase knowledgeBase, String modelName, PMMLContext context);- > -Create AbstractPMMLModelExecutor that implement the above interface and declare an abstract method- > -PMML4Result evaluate(final KieBase knowledgeBase, KiePMMLModel model, PMMLContext context)- > -AbstractPMMLModelExecutor should then use KnoweledgeBaseUtils to retrieve the KiePMMLModel and invoke/delegate to actual implementations- > -Actual implementations should then extend AbstractPMMLModelExecutor- > The PMMLModelExecutor API should be intended as private API, i.e. users should not invoke it directly, nor they should need to retrieve the KiePMMLModel. > Unfortunately, for the moment being the KiePMMLModel is needed to retrieve the actual implementation of PMMLModelExecutor, so it is not possible to invoke > {code:java} > PMMLModelExecutor.evaluate(...) > {code} > on it using only the model name without retrieve the KiePMMLModel itself before. > For the moment being this ticket will remove usage of PMMLModelExecutor implementation inside integrations tests. > Moreover, there will also be a small name refactoring to uniform the name of the classes in the hierarchy, so that the main interface will be > PMMLModelEvaluator, and all the implementing class will end with "Evaluator" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13554) Test Cases of JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters

by Parul Sharma (Jira)

Parul Sharma created WFLY-13554: ----------------------------------- Summary: Test Cases of JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters Key: WFLY-13554 URL: https://issues.redhat.com/browse/WFLY-13554 Project: WildFly Issue Type: Bug Reporter: Parul Sharma Assignee: Parul Sharma Test case for this issue https://issues.redhat.com/browse/WFLY-13375, if connection factory or JMS destination is configured for third party resource adapter #13241 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1151) Automate Workload logs Side by Side

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1151?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1151: ------------------------------------- Assignee: Hayk Hovsepyan > Automate Workload logs Side by Side > ----------------------------------- > > Key: SWSQE-1151 > URL: https://issues.redhat.com/browse/SWSQE-1151 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020