November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3294) [DMN Designer] Runtime issues [7.2.0.Final]

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3294: -------------------------------------- Summary: [DMN Designer] Runtime issues [7.2.0.Final] Key: DROOLS-3294 URL: https://issues.jboss.org/browse/DROOLS-3294 Project: Drools Issue Type: Epic Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ] Toni Rikkola reassigned DROOLS-2373: ------------------------------------ Assignee: Toni Rikkola (was: Michael Anstis) > BRL "is contained in the (comma separated) list" does not produce multiselect dropdown > -------------------------------------------------------------------------------------- > > Key: DROOLS-2373 > URL: https://issues.jboss.org/browse/DROOLS-2373 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor > Affects Versions: 7.6.0.Final > Environment: Tomcat 8.5 / RHEL 7 > Reporter: Yannick Geerts > Assignee: Toni Rikkola > Priority: Major > > Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs > *Edited* > The problem is that in the piece of code below the expression {{column.getOperator()}} returns null. > {{BRLConditionVariableColumnConverter#convertColumn}} > {code:java} > if (OperatorsOracle.operatorRequiresList(column.getOperator())) { > return newMultipleSelectEnumColumn(factType, > factField, > column, > access, > gridWidget); > } else { > return newSingleSelectionEnumColumn(factType, > factField, > dataType, > column, > access, > gridWidget); > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2373) BRL "is contained in the (comma separated) list" does not produce multiselect dropdown

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2373?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2373: --------------------------------- Sprint: 2018 Week 45-47 > BRL "is contained in the (comma separated) list" does not produce multiselect dropdown > -------------------------------------------------------------------------------------- > > Key: DROOLS-2373 > URL: https://issues.jboss.org/browse/DROOLS-2373 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor > Affects Versions: 7.6.0.Final > Environment: Tomcat 8.5 / RHEL 7 > Reporter: Yannick Geerts > Assignee: Toni Rikkola > Priority: Major > > Google groups link: https://groups.google.com/forum/#!topic/drools-usage/VElZ3KAZMIs > *Edited* > The problem is that in the piece of code below the expression {{column.getOperator()}} returns null. > {{BRLConditionVariableColumnConverter#convertColumn}} > {code:java} > if (OperatorsOracle.operatorRequiresList(column.getOperator())) { > return newMultipleSelectEnumColumn(factType, > factField, > column, > access, > gridWidget); > } else { > return newSingleSelectionEnumColumn(factType, > factField, > dataType, > column, > access, > gridWidget); > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3291) [DMN Designer] Allowed Values just for built in types

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3291?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3291: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Allowed Values just for built in types > ----------------------------------------------------- > > Key: DROOLS-3291 > URL: https://issues.jboss.org/browse/DROOLS-3291 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > Citing form spec: > {code} > ItemDefinition element SHALL be defined using only one of the alternative ways: > - reference to a built-in or imported typeRef, possibly restricted with allowedValues; > - composition of ItemDefinition elements. > {code} > Because of the above, I think we should hide constraint component for ItemDefinitions of type structure. > h2. Manual Acceptance test > - User is not able to add constraint (allowedValues) for item definition of Structure type > -- Create form scratch > -- Change existing that already had constraints -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3268) [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3268?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3268: ------------------------------------- [~dadossan] Hi I amrked jira as resolved and set fix version as the PR was merged, thanks one more time. > [DMN Designer] Data-types: Check for use of built-in-type should be case sensitive > ---------------------------------------------------------------------------------- > > Key: DROOLS-3268 > URL: https://issues.jboss.org/browse/DROOLS-3268 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Fix For: 7.15.0.Final > > > On the Data Types dialog, creating a type/field called "Number" with an uppercase "N" should be allowed. FEEL/DMN is type sensitive, and only "number" lower case is reserved word. Check if the problem also happens for other types, except for "Any" and "Null" that have an upper case initial. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3292) [DMN Designer] Custom Data Type dialog can be invoked from read only mode

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3292?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3292: -------------------------------------- Assignee: Michael Anstis (was: Guilherme Carreiro) > [DMN Designer] Custom Data Type dialog can be invoked from read only mode > ------------------------------------------------------------------------- > > Key: DROOLS-3292 > URL: https://issues.jboss.org/browse/DROOLS-3292 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Trivial > Labels: drools-tools > Attachments: Screenshot from 2018-11-09 09-25-38.png > > > In the attachment is shown manage button is not disabled in read only mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3292) [DMN Designer] Custom Data Type dialog can be invoked from read only mode

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3292?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3292: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Custom Data Type dialog can be invoked from read only mode > ------------------------------------------------------------------------- > > Key: DROOLS-3292 > URL: https://issues.jboss.org/browse/DROOLS-3292 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Trivial > Labels: drools-tools > Attachments: Screenshot from 2018-11-09 09-25-38.png > > > In the attachment is shown manage button is not disabled in read only mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11317) When disabling context on balancer, its status will never switch to 'disabled'

by Jan Kašík (Jira)

Jan Kašík created WFLY-11317: -------------------------------- Summary: When disabling context on balancer, its status will never switch to 'disabled' Key: WFLY-11317 URL: https://issues.jboss.org/browse/WFLY-11317 Project: WildFly Issue Type: Bug Components: mod_cluster Affects Versions: 15.0.0.Alpha1 Reporter: Jan Kašík Assignee: Radoslav Husar When disabling context on proxy for given node, no more requests are routed to this node from balancer. The status of context shown on console will however never switch to "disabled". {code} /subsystem=undertow/configuration=filter/mod-cluster=modcluster:read-resource(include-runtime=true, recursive=true, recursive-depth=100) ... node" => { "wildfly-15.0.0.Alpha1-SNAPSHOT-1" => { "aliases" => [ "default-host", "localhost" ], "cache-connections" => 40, "elected" => 2, "flush-packets" => false, "load" => 66, "load-balancing-group" => undefined, "max-connections" => 40, "open-connections" => 4, "ping" => 10, "queue-new-requests" => true, "read" => 0L, "request-queue-size" => 1000, "status" => "NODE_UP", "timeout" => 0, "ttl" => 60L, "uri" => "ajp://172.17.0.2:8009/?#", "written" => 0L, "context" => { "/clusterbench" => { "requests" => 0, "status" => "enabled" }, "/" => { "requests" => 0, "status" => "enabled" }, "/wildfly-services" => { "requests" => 0, "status" => "enabled" } } }, ... {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3269) [DMN Designer] Context: Default can be any expression type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3269: ------------------------------------- [~manstis] Ok, I know what is my concern, hope will be able explain below. If you have a look on the attached screenshot, the top level Context Header Cell says the context returns a number. It is correct because the Decision node holds {{<variable>}} with {{typeRef}} to {{number}}. The problem is that the {{context}} has {{typeRef}} to {{string}} even when the holding Decision returns {{number}}. Am I clear now please? Reading my comment, maybe it is different issue we are solving that block proper fix of this one. > [DMN Designer] Context: Default can be any expression type > ---------------------------------------------------------- > > Key: DROOLS-3269 > URL: https://issues.jboss.org/browse/DROOLS-3269 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Qclt6jQn.dmn, Screenshot from 2018-11-09 08-16-34.png > > > The "default" box can be any type of expression, specially decision tables and nested contexts. > Furthermore the "default" box on contexts is optional. We must provide a way for it to be removed. When support for _any_ type of expression we'll be able to have a {{null}} value for the expression so this should fix itself. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1942) [DMN Editor] InformationItem's "Name" is always the same as the containing node

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1942?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-1942: ------------------------------------- Can confirm is fixed by the linked PR. > [DMN Editor] InformationItem's "Name" is always the same as the containing node > ------------------------------------------------------------------------------- > > Key: DROOLS-1942 > URL: https://issues.jboss.org/browse/DROOLS-1942 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > Priority: Blocker > Labels: drools-tools > > Whilst an {{InformationItem}} Node has a "Name" its value is always the same as the containing Node's "Name" (for {{InputData}}, {{Decision}} and {{BusinessKnowledgeModel}}). {{ContextEntry}}'s "Name" are not the same as outer most node's "Name" (as a {{ContextEntry}} is contained within a {{Context}} and not directly in a node itself). > It is proposed that this synchronization should be handled in the "Stunner to (org.kie) DMN model" marshalling. Therefore we need to remove the "Name" {{@FormField}} from {{InformationItem}}. > [~tari_manga] [~tirelli] Please confirm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 November 2018