March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3777) Receiving error IndexOutOfBoundsException on jdk11

by Yevgeniy Fomin (Jira)

Yevgeniy Fomin created DROOLS-3777: -------------------------------------- Summary: Receiving error IndexOutOfBoundsException on jdk11 Key: DROOLS-3777 URL: https://issues.jboss.org/browse/DROOLS-3777 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.20.0.Final Environment: * jdk11 * Apache Maven 3.5.4 (Red Hat 3.5.4-4) Reporter: Yevgeniy Fomin Assignee: Michael Anstis Attachments: Error log array There is IndexOutOfBoundsException on AddInputClauseCommandTest and AddOutputClauseCommandTest if they are run on jdk 11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3776) Remove KieSession creation to run a DMN simulation

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3776: ------------------------------------- Summary: Remove KieSession creation to run a DMN simulation Key: DROOLS-3776 URL: https://issues.jboss.org/browse/DROOLS-3776 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Scenario tool requires to have a default KieSession (= stateful) to obtain the DMNRuntime. It should be possible to obtain directly the DMNRuntime from the KieContainer -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4376) Deprecation of AbstractCapability should not be visible to non-deprecated API within RuntimeCapability subclass

by Paul Ferraro (Jira)

Paul Ferraro created WFCORE-4376: ------------------------------------ Summary: Deprecation of AbstractCapability should not be visible to non-deprecated API within RuntimeCapability subclass Key: WFCORE-4376 URL: https://issues.jboss.org/browse/WFCORE-4376 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 8.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro AbstractCapability -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3713) [DMN Designer] Automatic layout is reordering nodes inside Decision Service

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3713?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3713: ------------------------------------- [~dadossan] is this really task for [~mfusco], shouldn't be the assigned one please? > [DMN Designer] Automatic layout is reordering nodes inside Decision Service > --------------------------------------------------------------------------- > > Key: DROOLS-3713 > URL: https://issues.jboss.org/browse/DROOLS-3713 > Project: Drools > Issue Type: Enhancement > Affects Versions: 7.20.0.Final > Reporter: Daniel José dos Santos > Assignee: Mario Fusco > Priority: Major > Attachments: screenshot_from_2019-02-28_09-28-58.png > > > The automatic layout is reordering nodes inside decision service, which shouldn't happen. The entire Decision Service should be considered as a "single node". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2974) CLI completion after one or more spaces gives confusing result

by Jean-Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFCORE-2974?page=com.atlassian.jira.plugi... ] Jean-Francois Denise closed WFCORE-2974. ---------------------------------------- Resolution: Won't Fix Edge case that could introduce regression in completion. Closing it, feel free to re-open and increase priority if that is a concern. Thanks. > CLI completion after one or more spaces gives confusing result > -------------------------------------------------------------- > > Key: WFCORE-2974 > URL: https://issues.jboss.org/browse/WFCORE-2974 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Beta26 > Reporter: Chao Wang > Assignee: Jean-Francois Denise > Priority: Minor > > CLI completion after one or more spaces gives confusing result. > {noformat} > [standalone@localhost:9990 /] /sub[space]TabKey Here > above completion returns result: > [standalone@localhost:9990 /] /sub ystem= > It seems the space before TabKey is recognized as character 's'. > Go on for a second TabKey, it will not list any subsystem candidates. > {noformat} > I think the first completion is not necessary as the {{sub}} with a following space is not a valid path. It'd better stop there rather than return completion result {{/sub ystem=}}. But this is a minor case. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3713) [DMN Designer] Automatic layout is reordering nodes inside Decision Service

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3713?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3713: -------------------------------- Tester: Jozef Marko > [DMN Designer] Automatic layout is reordering nodes inside Decision Service > --------------------------------------------------------------------------- > > Key: DROOLS-3713 > URL: https://issues.jboss.org/browse/DROOLS-3713 > Project: Drools > Issue Type: Enhancement > Affects Versions: 7.20.0.Final > Reporter: Daniel José dos Santos > Assignee: Mario Fusco > Priority: Major > Attachments: screenshot_from_2019-02-28_09-28-58.png > > > The automatic layout is reordering nodes inside decision service, which shouldn't happen. The entire Decision Service should be considered as a "single node". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3713) [DMN Designer] Automatic layout is reordering nodes inside Decision Service

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3713?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3713: -------------------------------- Affects Version/s: 7.20.0.Final > [DMN Designer] Automatic layout is reordering nodes inside Decision Service > --------------------------------------------------------------------------- > > Key: DROOLS-3713 > URL: https://issues.jboss.org/browse/DROOLS-3713 > Project: Drools > Issue Type: Enhancement > Affects Versions: 7.20.0.Final > Reporter: Daniel José dos Santos > Assignee: Mario Fusco > Priority: Major > Attachments: screenshot_from_2019-02-28_09-28-58.png > > > The automatic layout is reordering nodes inside decision service, which shouldn't happen. The entire Decision Service should be considered as a "single node". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2974) CLI completion after one or more spaces gives confusing result

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFCORE-2974?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-2974: ---------------------------------------- [~jdenise] If this one is not going to get fix, could you close it, please? Thanks > CLI completion after one or more spaces gives confusing result > -------------------------------------------------------------- > > Key: WFCORE-2974 > URL: https://issues.jboss.org/browse/WFCORE-2974 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 3.0.0.Beta26 > Reporter: Chao Wang > Assignee: Jean-Francois Denise > Priority: Minor > > CLI completion after one or more spaces gives confusing result. > {noformat} > [standalone@localhost:9990 /] /sub[space]TabKey Here > above completion returns result: > [standalone@localhost:9990 /] /sub ystem= > It seems the space before TabKey is recognized as character 's'. > Go on for a second TabKey, it will not list any subsystem candidates. > {noformat} > I think the first completion is not necessary as the {{sub}} with a following space is not a valid path. It'd better stop there rather than return completion result {{/sub ystem=}}. But this is a minor case. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3891) Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem

by Michal Petrov (Jira)

[ https://issues.jboss.org/browse/WFCORE-3891?page=com.atlassian.jira.plugi... ] Michal Petrov commented on WFCORE-3891: --------------------------------------- [~jamezp] in that case would it be ok to make "reserved" naming pattern that users couldn't use? Otherwise the issue remains that the subsystem cannot detect and deal with a naming collision and a 100% unique name is not possible. > Cannot create xml-formatter and json-formatter with the same name as existing resources in logging subsystem > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3891 > URL: https://issues.jboss.org/browse/WFCORE-3891 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Nikoleta Žiaková > Assignee: James Perkins > Priority: Major > > When trying to create an {{xml-formatter}} or {{json-formatter}} with the same name as another resource (e.g. a {{file-handler}}), the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=aaa.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/xml-formatter=test:add > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"dateFormat\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > Similarly vice-versa, when trying to create another resource in logging subsystem with the same name as an {{xml-formatter}} or a {{json-formatter}}, the operation fails: > {code} > [standalone@localhost:9990 /] /subsystem=logging/json-formatter=test:add > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException: No property \"pattern\" setter found for formatter \"test\"", > "rolled-back" => true > } > {code} > The same scenario works for e.g. {{pattern-formatter}}: > {code} > [standalone@localhost:9990 /] /subsystem=logging/file-handler=test:add(file={path=test.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/pattern-formatter=test:add > {"outcome" => "success"} > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3187) add-user.sh tool prints unexpected characters if arrow keys are pushed during interactive mode

by Miroslav Novak (Jira)

[ https://issues.jboss.org/browse/WFCORE-3187?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFCORE-3187: ---------------------------------------- [~mmarusic] Is there any update on this? Will it be closed? > add-user.sh tool prints unexpected characters if arrow keys are pushed during interactive mode > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-3187 > URL: https://issues.jboss.org/browse/WFCORE-3187 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Affects Versions: 3.0.0.Beta29 > Reporter: Marek Marusic > Assignee: Marek Marusic > Priority: Minor > > *Description of problem:* > add-user.sh tool prints unexpected characters if arrow keys are pushed during interactive mode. > *How reproducible:* > Always > *Steps to Reproduce:* > # ./add-user.sh > # press ←,↑,→,↓ keys > *Actual results:* > {noformat} > [mkopecky@localhost bin]$ ./add-user.sh > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): ^[[D^[[A^[[C^[[B > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 March 2019