December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5874) Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5874?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5874: -------------------------------- Affects Version/s: 7.47.0.Final > Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5874 > URL: https://issues.redhat.com/browse/DROOLS-5874 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.47.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Fix For: 7.47.0.Final > > > This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... > > The problem is if the literal value passed as argument to called method contains quotes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14093) Deprecate XTS subsystem

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-14093?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-14093: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13758 > Deprecate XTS subsystem > ----------------------- > > Key: WFLY-14093 > URL: https://issues.redhat.com/browse/WFLY-14093 > Project: WildFly > Issue Type: Task > Components: XTS > Affects Versions: 22.0.0.Alpha1 > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > XTS spec does not develop for a long time and other technologies are better of use nowadays. > The deprecation does not mean removing or changing the functionality, but rather a step to gather information how users utilize this functionality and of course as an announcement that this move is planned from our side. > We should deprecate WS-AT, WS-BA and xtsbridge and finally compensations as it depends on the XTS code and JAX-WS abilities. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14128) Upgrade opentracing-interceptors from 0.0.4 to 0.0.4.1

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-14128?page=com.atlassian.jira.plugi... ] Chao Wang updated WFLY-14128: ----------------------------- Description: Tag: https://github.com/opentracing-contrib/java-interceptors/tree/v0.0.4.1 Diff: https://github.com/opentracing-contrib/java-interceptors/compare/v0.0.4..... Commit hash: 97757b49c72a221590a1cd88dc5383d3cfb25158 was: Tag: https://github.com/opentracing-contrib/java-interceptors/tree/v0.1.0 Diff: https://github.com/opentracing-contrib/java-interceptors/compare/v0.0.4..... > Upgrade opentracing-interceptors from 0.0.4 to 0.0.4.1 > ------------------------------------------------------ > > Key: WFLY-14128 > URL: https://issues.redhat.com/browse/WFLY-14128 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Reporter: Chao Wang > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: downstream_dependency > > Tag: https://github.com/opentracing-contrib/java-interceptors/tree/v0.0.4.1 > Diff: https://github.com/opentracing-contrib/java-interceptors/compare/v0.0.4..... > Commit hash: 97757b49c72a221590a1cd88dc5383d3cfb25158 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5874) Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5874?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5874: -------------------------------- Description: This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... The problem is if the literal value passed as argument to called method has quotes as starting and ending character. was: This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... The problem is if the literal value passed as argument to called method contains quotes. > Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5874 > URL: https://issues.redhat.com/browse/DROOLS-5874 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.47.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Fix For: 7.47.0.Final > > > This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... > > The problem is if the literal value passed as argument to called method has quotes as starting and ending character. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4217) ManagementAuthenticationUsersTestCase fails with Elytron profile

by Martin Choma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4217?page=com.atlassian.jira.plug... ] Martin Choma updated WFCORE-4217: --------------------------------- Steps to Reproduce: {code} cd testsuite/standalone/ mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase {code} was: cd testsuite/standalone/ mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase > ManagementAuthenticationUsersTestCase fails with Elytron profile > ---------------------------------------------------------------- > > Key: WFCORE-4217 > URL: https://issues.redhat.com/browse/WFCORE-4217 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Affects Versions: 7.0.0.Alpha5 > Reporter: Martin Choma > Priority: Major > > {noformat} > cd testsuite/standalone/ > mvn test -Delytron -Dtest=ManagementAuthenticationUsersTestCase > {noformat} > {noformat} > [INFO] Running null > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in null > [ERROR] Failure when constructing test Time elapsed: 0.003 s <<< FAILURE! > java.lang.AssertionError: > WFLYCTL0216: Management resource '[ > ("core-service" => "management"), > ("security-realm" => "ManagementRealm") > ]' not found > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.executeForSuccess(ManagementAuthenticationUsersServerSetupTask.java:113) > at org.jboss.as.test.integration.credential.store.ManagementAuthenticationUsersServerSetupTask.setup(ManagementAuthenticationUsersServerSetupTask.java:65) > at org.wildfly.core.testrunner.WildflyTestRunner.runSetupTasks(WildflyTestRunner.java:121) > at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:107) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) > [INFO] > [INFO] Results: > [INFO] > [ERROR] Failures: > [ERROR] WFLYCTL0216: Management resource '[ > ("core-service" => "management"), > ("security-realm" => "ManagementRealm") > ]' not found > [INFO] > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 > [INFO] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5874) Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5874?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5874: -------------------------------- Description: This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... The problem is if the literal value passed as argument to called method contains quotes. was:For more details see [comment|https://issues.redhat.com/browse/RHPAM-2972?focusedCommentId=1413...] > Guided Rule Editor: Call method on XYZ with literal value containing quotes does not re-open correctly > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5874 > URL: https://issues.redhat.com/browse/DROOLS-5874 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Fix For: 7.47.0.Final > > > This Jira is about corner case described properly here in [Jira comment|[https://github.com/kiegroup/drools/pull/3227#issuecomment-725976... > > The problem is if the literal value passed as argument to called method contains quotes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5121) Requires click Build button to update column field type

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5121?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5121: ---------------------------------------- As of today, sanity check for 7.47.0.Final, the behaviour is still the same as originally reported. New proof, step 1: !Screenshot 2020-12-02 at 16.40.35.png|thumbnail! result: !Screenshot 2020-12-02 at 16.40.47.png|thumbnail! > Requires click Build button to update column field type > ------------------------------------------------------- > > Key: DROOLS-5121 > URL: https://issues.redhat.com/browse/DROOLS-5121 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Matteo Mortari > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: ScesimRequiresBuildButtonToUpdateColumn.mov, Screenshot 2020-12-02 at 16.40.35.png, Screenshot 2020-12-02 at 16.40.47.png > > > as attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5848) CallMethod with ActionFieldFunctions does not compile

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5848?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5848: -------------------------------- Tester: Jozef Marko Target Release: (was: 7.10.0.GA) > CallMethod with ActionFieldFunctions does not compile > ------------------------------------------------------ > > Key: DROOLS-5848 > URL: https://issues.redhat.com/browse/DROOLS-5848 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > [DROOLS-3893] [Guided Decision Table] Call method on is not generated - Red Hat Issue Tracker > > The DROOLS-3893 needs an additional fix for Call methods setups where the CallMethod uses ActionFieldFunctions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5875) Create a rete/phreak groupBy node

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5875: ----------------------------------- Summary: Create a rete/phreak groupBy node Key: DROOLS-5875 URL: https://issues.redhat.com/browse/DROOLS-5875 Project: Drools Issue Type: Feature Request Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (ELY-2049) Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial

by Boris Unckel (Jira)

[ https://issues.redhat.com/browse/ELY-2049?page=com.atlassian.jira.plugin.... ] Boris Unckel updated ELY-2049: ------------------------------ Description: The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions. Examples: [Undertow|https://issues.redhat.com/browse/UNDERTOW-1815] [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...] line 2048 The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs. Current code: {code:java} public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) { ProtectionDomain deniedDomain = null; if (domains != null) for (ProtectionDomain domain : domains) { if (! domain.implies(permission)) { final CodeSource codeSource = domain.getCodeSource(); final ClassLoader classLoader = domain.getClassLoader(); final Principal[] principals = domain.getPrincipals(); if (principals == null || principals.length == 0) { access.accessCheckFailed(permission, codeSource, classLoader); } else { access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals)); } if (deniedDomain == null && ! LOG_ONLY) { deniedDomain = domain; } } } return deniedDomain; } {code} was: The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions. Example: [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...] line 2048 The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs. Current code: {code:java} public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) { ProtectionDomain deniedDomain = null; if (domains != null) for (ProtectionDomain domain : domains) { if (! domain.implies(permission)) { final CodeSource codeSource = domain.getCodeSource(); final ClassLoader classLoader = domain.getClassLoader(); final Principal[] principals = domain.getPrincipals(); if (principals == null || principals.length == 0) { access.accessCheckFailed(permission, codeSource, classLoader); } else { access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals)); } if (deniedDomain == null && ! LOG_ONLY) { deniedDomain = domain; } } } return deniedDomain; } {code} > Add trace capability to o.w.s.m.WildFlySecurityManager findAccessDenial > ----------------------------------------------------------------------- > > Key: ELY-2049 > URL: https://issues.redhat.com/browse/ELY-2049 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Security Manager > Affects Versions: 1.13.2.Final > Reporter: Boris Unckel > Priority: Major > > The current implementation is very strong for regular cases. It works fine to display missing permissions when CodeSource and/or ClassLoader are correctly set to the checked protection domain. If one of those is missing and there is no good exception handling, it is impossible to track down missing permissions. > Examples: > [Undertow|https://issues.redhat.com/browse/UNDERTOW-1815] > [java.io.File|https://github.com/openjdk/jdk/blob/jdk-11%2B28/src/java.bas...] > line 2048 > The idea is to provide a yielded trace log and provide the missing permission, the full protection domain and a dummy exception to have stack trace where this occurs. > Current code: > {code:java} > public static ProtectionDomain findAccessDenial(final Permission permission, final ProtectionDomain... domains) { > ProtectionDomain deniedDomain = null; > if (domains != null) for (ProtectionDomain domain : domains) { > if (! domain.implies(permission)) { > final CodeSource codeSource = domain.getCodeSource(); > final ClassLoader classLoader = domain.getClassLoader(); > final Principal[] principals = domain.getPrincipals(); > if (principals == null || principals.length == 0) { > access.accessCheckFailed(permission, codeSource, classLoader); > } else { > access.accessCheckFailed(permission, codeSource, classLoader, Arrays.toString(principals)); > } > if (deniedDomain == null && ! LOG_ONLY) { > deniedDomain = domain; > } > } > } > return deniedDomain; > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

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 December 2020