June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4138) Building a KJAR using Decision Table Templates throws NPE

by Carl Mes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4138?page=com.atlassian.jira.plugi... ] Carl Mes commented on DROOLS-4138: ---------------------------------- Update: I think I might have found the root cause for why the "drools.trimCellsInDTable" option is not working for templates. The logic that implements this property is found in [KnowledgeBuilderImpl.java#L405|https://github.com/kiegroup/drools/blob/7....], however the templates are generated using the logic on [KnowledgeBuilderImpl.java#L405|https://github.com/kiegroup/drools/blob/7....] (loadFromInputStreamWithTemplates), so this property is unreachable when building templates (drt + xlsx). > Building a KJAR using Decision Table Templates throws NPE > --------------------------------------------------------- > > Key: DROOLS-4138 > URL: https://issues.jboss.org/browse/DROOLS-4138 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final, 7.23.0.Final > Reporter: Carl Mes > Assignee: Mario Fusco > Priority: Major > Attachments: DecisionTableConfigurationImpl.java > > > Steps to building a new KJar by defining Resource objects and adding then using KieFileSystem.write(), if a Decision Table Template resource type is added then we get a null pointer exception when the KieBuilder.buildAll() method is invoked. > Sample code that demonstrates this error can be found here: https://github.com/carlmes/decision-table-template, specifically the notes in [TestDecisionTableBuild.java|https://github.com/carlmes/decision-table-tem...]. > Red Hat support case: https://access.redhat.com/support/cases/#/case/02397413 > I have created a proposed fix in [DecisionTableConfigurationImpl.java|https://github.com/kiegroup/drools/bl...], by implementing the missing properties in the fromProperties and toProperties methods. Please see attached updated file that has been tested to fix the issue locally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8714) AZURE_PING integration with Elytron's CredentialStore

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-8714?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8714: --------------------------------- Summary: AZURE_PING integration with Elytron's CredentialStore (was: AZURE_PING integrattion with Elytron's CredentialStore) > AZURE_PING integration with Elytron's CredentialStore > ----------------------------------------------------- > > Key: WFLY-8714 > URL: https://issues.jboss.org/browse/WFLY-8714 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 11.0.0.Alpha1, 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > Currently, the passphrases are stored in the server profile, however they need to be consumed from Elytron credential store. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4516) The expression for secret value under server-identities in test-security-realm does not work .

by Indrajit Ingawale (Jira)

Indrajit Ingawale created WFCORE-4516: ----------------------------------------- Summary: The expression for secret value under server-identities in test-security-realm does not work . Key: WFCORE-4516 URL: https://issues.jboss.org/browse/WFCORE-4516 Project: WildFly Core Issue Type: Bug Components: Remoting, Security Reporter: Indrajit Ingawale Assignee: Flavia Rainone The expression for secret value under server-identities in test-security-realm does not work , even though it shows "expressions-allowed" to true like below . ---------------------------- [standalone@localhost:9990 /] /core-service=management/security-realm=test-security-realm/server-identity=secret:read-resource-description() { "outcome" => "success", . . "attributes" => {. . . . . } , "value" => { "type" => STRING, "description" => "The secret / password - Base64 Encoded.", "expressions-allowed" => true, "required" => true, "nillable" => true, "alternatives" => ["credential-reference"], "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" } }, "operations" => undefined, "notifications" => undefined, "children" => {} } } ---------------------------- -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10872) Confusing error message when writing simple-load-provider attribute when dynamic load provider is present

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-10872?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10872: --------------------------------------- Agreed, this should just be a logging change, rather than auto creating and/or removing resources. Submitted a PR with this approach. > Confusing error message when writing simple-load-provider attribute when dynamic load provider is present > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-10872 > URL: https://issues.jboss.org/browse/WFLY-10872 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 14.0.0.Beta2, 17.0.0.Final > Reporter: Jan Kasik > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > Following should add simple load provider with factor=0: > {code} > /subsystem=modcluster/mod-cluster-config=configuration/:write-attribute(name=simple-load-provider, value=0) > {code} > Instead, this error shows up: > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"modcluster\"), > (\"proxy\" => \"default\"), > (\"load-provider\" => \"simple\") > ]' not found", > "rolled-back" => true > } > {code} > There is missing translation to create the resource, same is the situation for undefine operation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3731: ------------------------------------------- [~zhutaojiajia] Thanks so much for the explanation, it was very helpful! * WRT color coding: I asked about that, in response to [#https://issues.jboss.org/browse/DROOLS-3731?focusedCommentId=13741051&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13741051] regarding color coding the canvas nodes. I would think representing the state/status of a node using a color coding system should be applied consistently, so was just asking what happens in Scenario. * WRT overlays: This jira requires coverage for the 2 use cases that [~tirelli] mentions above in the May 31 comment. 1. Popovers for single test execution (similar to what you did for Scenario.) 2. Node status when several tests are executed. [~karreiro] Is there any additional information that you can provide for [~zhutaojiajia]. Side question: [~danielezonca] I know there was some discussion with [~porcelli] of showing test results in the message panels at the bottom (kind of like the junit runner) does that relate to any of this work? Thanks! > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, download (1).png, download.png, 屏幕快照 2019-06-11 下午3.02.19.png, 屏幕快照 2019-06-11 下午3.10.26.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4474) Missing path validation of a log file while update path

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4474?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4474: --------------------------------------- Sorry this looks like a markup formatting issue. Those "{{" and "}}" should not be there. The "\" will need to be escaped with a "\\" so it should be: {code} /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log}) {code} > Missing path validation of a log file while update path > -------------------------------------------------------- > > Key: WFCORE-4474 > URL: https://issues.jboss.org/browse/WFCORE-4474 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 9.0.0.Beta4 > Reporter: Vratislav Marek > Assignee: James Perkins > Priority: Major > > After the first successful set of a valid path, you can set an invalid path. > It is can be relative to that while "relative-to" parameter is overridden, the validator doesn't validate it. > Discovered on Windows. > A code block is divided, but it is holding sequence to reproduce. > _This works as expected._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:/server.log", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > :> at index 61: D:\\Tests\\clear\\wildfly-17.0.0.Beta1-SNAPSHOT\\standalone\\log\\C:server.log", > "rolled-back" => true > } > {code} > _Still works as expected. But After this successful write-attribute command, it that changing._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log}) > {"outcome" => "success"} > {code} > *Now there is a problem, it that not works as expected. The validator accepts invalid path.* > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > {code} > _But not accept all invalid paths._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:*server.log}) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.nio.file.InvalidPathException: Illegal char < > *> at index 2: C:*server.log", > "rolled-back" => true > } > {code} > _Verification if the unsuccessful update changes something. But not._ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\\server.log}) > {"outcome" => "success"} > {code} > _Verification if is really set in the property value. Yes_ > {code:bash} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:\\server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:/server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:/server.log"} > } > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:write-attribute(name=file,value={path=C:\server.log}) > {"outcome" => "success"} > [standalone@localhost:9990 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-attribute(name=file) > { > "outcome" => "success", > "result" => {"path" => "C:server.log"} > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4515) Double word of service in the thrown exception ServiceNotFoundException

by Vratislav Marek (Jira)

Vratislav Marek created WFCORE-4515: --------------------------------------- Summary: Double word of service in the thrown exception ServiceNotFoundException Key: WFCORE-4515 URL: https://issues.jboss.org/browse/WFCORE-4515 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Vratislav Marek Assignee: Darran Lofthouse The exception has in message double word service. {code} org.jboss.msc.service.ServiceNotFoundException: Service service org.wildfly.security.certificate-authority-account.FakeCaAccount not found {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-4144: ------------------------------------------------ [~manstis] I reproduced this issue in BC 7.14, but I don't get it why this happen in BC but not in Showcase. The code isn't the same? > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4138) Building a KJAR using Decision Table Templates throws NPE

by Carl Mes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4138?page=com.atlassian.jira.plugi... ] Carl Mes commented on DROOLS-4138: ---------------------------------- Thanks for the update. I attempted to add this new system property into my reproducer code here: https://github.com/carlmes/decision-table-template/blob/9c48582a0ae7012f7... Also, I made sure that I'm using the latest version of the Drools modules (as defined here: https://access.redhat.com/solutions/3363991), which appears to be Maven library version: 7.18.0.Final-redhat-00002 (see https://github.com/carlmes/decision-table-template/blob/9c48582a0ae7012f7...) Unfortunately I couldn't get this system property to work correctly on my reproducer codebase. > Building a KJAR using Decision Table Templates throws NPE > --------------------------------------------------------- > > Key: DROOLS-4138 > URL: https://issues.jboss.org/browse/DROOLS-4138 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.18.0.Final, 7.23.0.Final > Reporter: Carl Mes > Assignee: Mario Fusco > Priority: Major > Attachments: DecisionTableConfigurationImpl.java > > > Steps to building a new KJar by defining Resource objects and adding then using KieFileSystem.write(), if a Decision Table Template resource type is added then we get a null pointer exception when the KieBuilder.buildAll() method is invoked. > Sample code that demonstrates this error can be found here: https://github.com/carlmes/decision-table-template, specifically the notes in [TestDecisionTableBuild.java|https://github.com/carlmes/decision-table-tem...]. > Red Hat support case: https://access.redhat.com/support/cases/#/case/02397413 > I have created a proposed fix in [DecisionTableConfigurationImpl.java|https://github.com/kiegroup/drools/bl...], by implementing the missing properties in the fromProperties and toProperties methods. Please see attached updated file that has been tested to fix the issue locally. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4144) [DMN Designer] Imported model is broken after saving changes

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-4144?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-4144: ---------------------------------- Priority: Critical (was: Major) > [DMN Designer] Imported model is broken after saving changes > ------------------------------------------------------------ > > Key: DROOLS-4144 > URL: https://issues.jboss.org/browse/DROOLS-4144 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: a-2.dmn, a.dmn, error.log > > > When user imports some dmn model (see the attahced a.dmn and a-2.dmn) then he do some changes and save such imported model. He is unable to reopen such model. There is error in the server log. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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