January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4953) Make Drools and Kogito compatible with Java 12

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4953?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4953: -------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) (was: 2020 Week 04-06 (from Jan 20)) > Make Drools and Kogito compatible with Java 12 > ---------------------------------------------- > > Key: DROOLS-4953 > URL: https://issues.redhat.com/browse/DROOLS-4953 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1046) Automate Validation links https://github.com/kiali/kiali/issues/2014

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1046?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1046. ----------------------------------- Resolution: Done > Automate Validation links https://github.com/kiali/kiali/issues/2014 > -------------------------------------------------------------------- > > Key: SWSQE-1046 > URL: https://issues.redhat.com/browse/SWSQE-1046 > 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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4699) Supporting long value input

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4699?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4699: ------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) (was: 2019 Week 44-46 (from Okt 28), 2020 Week 04-06 (from Jan 20)) > Supporting long value input > --------------------------- > > Key: DROOLS-4699 > URL: https://issues.redhat.com/browse/DROOLS-4699 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Description here: > https://issues.jboss.org/browse/DROOLS-4574?focusedCommentId=13794570&pag... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2147) Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-2147?page=com.atlassian.jira.plug... ] Yeray Borges commented on WFCORE-2147: -------------------------------------- Glad to hear you were able to do the backport. This feature was completely merged and will be included in WF19. You are using WildFly 12, it is probably advisable to update to a more recent release and then keep up to date on the releases. > Impossible to use environment variables or system properties in permissions.xml and jboss-permissions.xml > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2147 > URL: https://issues.redhat.com/browse/WFCORE-2147 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Adrian Boangiu > Assignee: Yeray Borges > Priority: Major > Fix For: 11.0.0.Beta7 > > > Without this feature it is impossible to migrate "variable" Java file permissions such as: > {noformat} > permission java.io.FilePermission "${java.io.tmpdir}","read"; > permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete"; > permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete"; > {noformat} > that were defined in Java policy file in previous verions of JBoss. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-4924: ------------------------------------------- Note: "without bind variable" may not be the only condition. I confirmed a materialized lambda with some complex RHS without bind variable. > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-12980: ----------------------------------------- Assignee: Bartosz Baranowski > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Bartosz Baranowski > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12980) Full reload is needed after microprofile-jwt-smallrye subsystem removal

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12980?page=com.atlassian.jira.plugi... ] Bartosz Baranowski resolved WFLY-12980. --------------------------------------- Resolution: Explained > Full reload is needed after microprofile-jwt-smallrye subsystem removal > ----------------------------------------------------------------------- > > Key: WFLY-12980 > URL: https://issues.redhat.com/browse/WFLY-12980 > Project: WildFly > Issue Type: Bug > Components: MP JWT > Reporter: Jan Kasik > Assignee: Bartosz Baranowski > Priority: Major > > When user is removing MP subsystem, full reload is required. This is partly a benefit because it provides a fast fail solution for deployments which requires classes from this subsystem. On the other hand, reload might not be feasible for user under in their current conditions. This is why it has to be reduced as much as possible. > Is there other way to provide fast fail without requiring full reload? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4924: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4924) LambdaConsequence without bind variable is not materialized

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4924?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-4924: -------------------------------------- Sprint: (was: 2020 Week 04-06 (from Jan 20)) > LambdaConsequence without bind variable is not materialized > ----------------------------------------------------------- > > Key: DROOLS-4924 > URL: https://issues.redhat.com/browse/DROOLS-4924 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > LambdaConsequence like this is not materialized. > {code:java} > D.execute(() -> { > System.out.println("Hello"); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4956) Normarize rule constraints for property reactivity and indexing

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-4956: ----------------------------------------- Summary: Normarize rule constraints for property reactivity and indexing Key: DROOLS-4956 URL: https://issues.redhat.com/browse/DROOLS-4956 Project: Drools Issue Type: Bug Components: core engine, executable model Affects Versions: 7.31.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco Having a constraint like {code:java} Person( name == "Toshiya" ) {code} is not really the same thing as {code:java} Person( "Toshiya" == name ) {code} In the second case not only you don't have property reactivity, but also you don't have indexing. This an inconsistent behaviour and hoping to fix it with a "normalization" phase where the second constraint got rewritten like the first before being analyzed by property reactivity and indexing. -- 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 January 2020