February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5051) Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5051?page=com.atlassian.jira.plug... ] Toshiya Kobayashi moved RHDM-1236 to DROOLS-5051: ------------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-5051 (was: RHDM-1236) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: core engine (was: BRE) Affects Version/s: 7.33.0.Final (was: 7.6.0.GA) QE Status: NEW > Mvel type coercion and rounding behavior compatibility between mvel 2.2.8 and 2.4.3 > ----------------------------------------------------------------------------------- > > Key: DROOLS-5051 > URL: https://issues.redhat.com/browse/DROOLS-5051 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: support > > I have rule like as: > ========= > rule "My Rule" > no-loop true > dialect "mvel" > when > $info : MyInfo() > then > modify ($info) { > setResult(15 * Math.round( new BigDecimal("49.4") ) / 100 ) > } > end > ========= > If I exeucte this rule in BRMS 6.4.x release, I will get 7.35 in the reponse . But if I execute same rule in RHDM 7.4.+ release I will 7 in the response. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4841) Logging subsystem capabilities do not work correctly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4841?page=com.atlassian.jira.plug... ] James Perkins commented on WFCORE-4841: --------------------------------------- [~brian.stansberry] yes. I was going to file a JIRA for that part. It seemed weird when I was debugging it. I just wanted to finish this for now, then I'll write a simple test example that fails. > Logging subsystem capabilities do not work correctly > ---------------------------------------------------- > > Key: WFCORE-4841 > URL: https://issues.redhat.com/browse/WFCORE-4841 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > With WFCORE-3337 the logging subsystem introduced capabilities. While looking at WFCORE-966 I determined the capabilities were not correctly implemented. In some cases invalid capabilities are allowed to be add in admin-only mode. In other cases they're allowed to be assigned even when invalid and running a full server. > The tests are also incorrect. They seemed correct as they checked for failed operations. However the result of the failure was not checked and some of the operations were failing, but not for the reasons expected. This was all a poor design on my part. > New tests need to be added. One thing I did notice was these tests don't seem to work in a static {{KernelServices}} test controller. For some reason when running against a logging profile the capability recorder seems to be empty. However using a manual mode test works fine. I believe this is just a flaw in the unit test controller. This will require the tests to be moved to manual mode tests so they can be test against an admin-only booted server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4841) Logging subsystem capabilities do not work correctly

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4841?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4841: ------------------------------------------ The bit about needing to use manual mode seems off, i.e. something we should sort. Not a super big priority though. > Logging subsystem capabilities do not work correctly > ---------------------------------------------------- > > Key: WFCORE-4841 > URL: https://issues.redhat.com/browse/WFCORE-4841 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > With WFCORE-3337 the logging subsystem introduced capabilities. While looking at WFCORE-966 I determined the capabilities were not correctly implemented. In some cases invalid capabilities are allowed to be add in admin-only mode. In other cases they're allowed to be assigned even when invalid and running a full server. > The tests are also incorrect. They seemed correct as they checked for failed operations. However the result of the failure was not checked and some of the operations were failing, but not for the reasons expected. This was all a poor design on my part. > New tests need to be added. One thing I did notice was these tests don't seem to work in a static {{KernelServices}} test controller. For some reason when running against a logging profile the capability recorder seems to be empty. However using a manual mode test works fine. I believe this is just a flaw in the unit test controller. This will require the tests to be moved to manual mode tests so they can be test against an admin-only booted server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4843) Add support for TLSv1.3 using the OpenSSL TLS provider

by Farah Juma (Jira)

Farah Juma created WFCORE-4843: ---------------------------------- Summary: Add support for TLSv1.3 using the OpenSSL TLS provider Key: WFCORE-4843 URL: https://issues.redhat.com/browse/WFCORE-4843 Project: WildFly Core Issue Type: Feature Request Reporter: Farah Juma Assignee: Farah Juma The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13085) Add support for TLSv1.3 using the OpenSSL TLS provider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13085?page=com.atlassian.jira.plugi... ] Farah Juma moved WFCORE-4843 to WFLY-13085: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13085 (was: WFCORE-4843) > Add support for TLSv1.3 using the OpenSSL TLS provider > ------------------------------------------------------ > > Key: WFLY-13085 > URL: https://issues.redhat.com/browse/WFLY-13085 > Project: WildFly > Issue Type: Feature Request > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13085) Add support for TLSv1.3 using the OpenSSL TLS provider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13085?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13085: ------------------------------ Component/s: Security > Add support for TLSv1.3 using the OpenSSL TLS provider > ------------------------------------------------------ > > Key: WFLY-13085 > URL: https://issues.redhat.com/browse/WFLY-13085 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4842) Add support for TLSv1.3 using the OpenSSL TLS provider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4842?page=com.atlassian.jira.plug... ] Farah Juma updated WFCORE-4842: ------------------------------- Component/s: Security > Add support for TLSv1.3 using the OpenSSL TLS provider > ------------------------------------------------------ > > Key: WFCORE-4842 > URL: https://issues.redhat.com/browse/WFCORE-4842 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Tristan Tarrant > Assignee: Farah Juma > Priority: Major > > The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4842) Add support for TLSv1.3 using the OpenSSL TLS provider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4842?page=com.atlassian.jira.plug... ] Farah Juma moved WFSSL-29 to WFCORE-4842: ----------------------------------------- Project: WildFly Core (was: WildFly OpenSSL) Key: WFCORE-4842 (was: WFSSL-29) Issue Type: Feature Request (was: Improvement) Workflow: GIT Pull Request workflow (was: classic default workflow) > Add support for TLSv1.3 using the OpenSSL TLS provider > ------------------------------------------------------ > > Key: WFCORE-4842 > URL: https://issues.redhat.com/browse/WFCORE-4842 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Tristan Tarrant > Assignee: Farah Juma > Priority: Major > > The WildFly OpenSSL provider does not register a handler for TLSv1.3. It should :) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13084) Populate the "OpenSSL" section in the Elytron documentation with information on how to use the OpenSSL TLS provider with Elytron

by Farah Juma (Jira)

Farah Juma created WFLY-13084: --------------------------------- Summary: Populate the "OpenSSL" section in the Elytron documentation with information on how to use the OpenSSL TLS provider with Elytron Key: WFLY-13084 URL: https://issues.redhat.com/browse/WFLY-13084 Project: WildFly Issue Type: Task Components: Security Reporter: Farah Juma Assignee: Farah Juma There is currently a blank OpenSSL.adoc file in the Elytron documentation. This should be populated with information on how to use the OpenSSL TLS provider with Elytron. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4841) Logging subsystem capabilities do not work correctly

by James Perkins (Jira)

James Perkins created WFCORE-4841: ------------------------------------- Summary: Logging subsystem capabilities do not work correctly Key: WFCORE-4841 URL: https://issues.redhat.com/browse/WFCORE-4841 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins With WFCORE-3337 the logging subsystem introduced capabilities. While looking at WFCORE-966 I determined the capabilities were not correctly implemented. In some cases invalid capabilities are allowed to be add in admin-only mode. In other cases they're allowed to be assigned even when invalid and running a full server. The tests are also incorrect. They seemed correct as they checked for failed operations. However the result of the failure was not checked and some of the operations were failing, but not for the reasons expected. This was all a poor design on my part. New tests need to be added. One thing I did notice was these tests don't seem to work in a static {{KernelServices}} test controller. For some reason when running against a logging profile the capability recorder seems to be empty. However using a manual mode test works fine. I believe this is just a flaw in the unit test controller. This will require the tests to be moved to manual mode tests so they can be test against an admin-only booted server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 February 2020