November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3254) Additional UI improvement/bugfixes

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3254?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3254: ---------------------------------- Sprint: 2018 Week 45-47 > Additional UI improvement/bugfixes > ---------------------------------- > > Key: DROOLS-3254 > URL: https://issues.jboss.org/browse/DROOLS-3254 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > This ticket contains the missing part of the original ticket https://issues.jboss.org/browse/DROOLS-3154 > See subtasks for details -- 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 Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3269?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3269: ---------------------------------------- Hi [~jomarko] could you please explain a little more? It looks like the DMN's {{Context}} has a {{typeRef}} of "string": {code:xml} <dmn:context id="_4B4416D7-9A05-4E24-9855-EAB423A5C5CB" typeRef="string"> {code} The {{DecisionTable}} {{OutputClause}} is also "string": {code:xml} <dmn:output id="_72AC8190-8D99-46E0-AF09-67B010C2935A" name="output-1" typeRef="string"> {code} I'd like to understand more specifically what the issue is (or more probably, what the requirement is). > [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-3150) Avoid multiple "editing" cell in header

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3150: --------------------------------- Summary: Avoid multiple "editing" cell in header (was: Race condition on clicks to enable inline editing into Scenario grid) > Avoid multiple "editing" cell in header > --------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3150) Avoid multiple "editing" cell in header

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3150: -------------------------------------- I checked the title of the Jira as the original issue was no longer valid. > Avoid multiple "editing" cell in header > --------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3150) Avoid multiple "editing" cell in header

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3150?page=com.atlassian.jira.plugi... ] Klara Kufova edited comment on DROOLS-3150 at 11/9/18 2:39 AM: --------------------------------------------------------------- I changed the title of the Jira as the original issue was no longer valid. was (Author: kkufova): I checked the title of the Jira as the original issue was no longer valid. > Avoid multiple "editing" cell in header > --------------------------------------- > > Key: DROOLS-3150 > URL: https://issues.jboss.org/browse/DROOLS-3150 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Attachments: 47010974-e8e16d80-d140-11e8-84dd-758c8253490f.png > > -- 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] please see the attached picture and dmn model, I have concern that default output context entry doesn't respect the output typeRef of the holding context. > [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-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 updated DROOLS-3269: -------------------------------- Attachment: Screenshot from 2018-11-09 08-16-34.png > [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-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 updated DROOLS-3269: -------------------------------- Attachment: Qclt6jQn.dmn > [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] (WFLY-11314) Look up of RemoteConnectionFactory with discovery-group is null

by Miroslav Novak (Jira)

Miroslav Novak created WFLY-11314: ------------------------------------- Summary: Look up of RemoteConnectionFactory with discovery-group is null Key: WFLY-11314 URL: https://issues.jboss.org/browse/WFLY-11314 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final Reporter: Miroslav Novak Assignee: ehsavoie Hugonnet Fix For: 15.0.0.Alpha1 If RemoteConnectionFactory is defined with discovery-group like (note that it's defined directly in messaging subsystem, not in <server>...</server>): {code} <subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0"> <discovery-group name="dg-group1" jgroups-channel="ee" jgroups-cluster="artemis-cluster" initial-wait-timeout="30000"/> <connection-factory name="RemoteConnectionFactory" discovery-group="dg-group1" entries="java:jboss/exported/jms/RemoteConnectionFactory java:/jms/RemoteConnectionFactory"/> </subsystem> {code} then it registers to JNDI "java:/jms/RemoteConnectionFactory" but with {{null}}. See JNDI view: {code} [standalone@localhost:9990 subsystem=naming] /subsystem=naming/:jndi-view ... "jms" => { "class-name" => "javax.naming.Context", "children" => { "RemoteConnectionFactory" => { "class-name" => "java.lang.Object", "value" => "null" }, {code} Result: If EE deployment looks up or injects such CF then it fails on NullPointerException. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3261) [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3261?page=com.atlassian.jira.plugi... ] Jozef Marko resolved DROOLS-3261. --------------------------------- Resolution: Done > [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue` > ------------------------------------------------------------------------------ > > Key: DROOLS-3261 > URL: https://issues.jboss.org/browse/DROOLS-3261 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Fix For: 7.14.0.Final > > Attachments: diagram.png, dtable.png > > > When the user persists the following diagram: > !diagram.png|thumbnail! > ..with the following Decision Table: > !dtable.png|thumbnail! > .. select the "Can drink beer?" header, set the default value as {{false}} and the file: > {quote} > <dmn:outputValues id="_A117F7DC-508C-4132-8F5F-8F8F2B0B489F"> > <dmn:text>false</dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_A4881AD1-7EDC-4B4D-AC00-078626795BA7" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > {quote} > ..and the expected behaviour is to persist the value {{false}} in the {{defaultOutputEntry}}. -- 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