November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2890: -------------------------------- Description: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} h2. Manual acceptance test - B&D new model, non default namespace - Import model with namespace - Import model without namespace was: The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) {quote} The Definitions properties that I think we need to expose are: * Id (probably read only) * name (needs to be editable; can default to the file name but should remain editable) * namespace * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. {quote} > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Fix For: 7.10.0.Final > > > The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) > {quote} > The Definitions properties that I think we need to expose are: > * Id (probably read only) > * name (needs to be editable; can default to the file name but should remain editable) > * namespace > * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. > {quote} > h2. Manual acceptance test > - B&D new model, non default namespace > - Import model with namespace > - Import model without namespace -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10741) Relicense Quickstarts and BOMs as Apache 2.0

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-10741?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-10741: ----------------------------------- Git Pull Request: https://github.com/wildfly/boms/pull/46, https://github.com/wildfly/quickstart/pull/316 > Relicense Quickstarts and BOMs as Apache 2.0 > -------------------------------------------- > > Key: WFLY-10741 > URL: https://issues.jboss.org/browse/WFLY-10741 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Reporter: Kabir Khan > Assignee: Eduardo Martins > Priority: Major > > There has been a bit back and forth on the bom and QS licenses in WF12, 13 and 14. For WF15, we should relicense them all (where possible) to Apache 2.0. > Note that we will need: > A LICENCE.txt in the root folder > The name of the license in the BOMs should be from the 'Full Name' column of https://spdx.org/licenses/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-480) Perf test comparison k8s cache on/off

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-480: ------------------------------------ Summary: Perf test comparison k8s cache on/off Key: SWSQE-480 URL: https://issues.jboss.org/browse/SWSQE-480 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Michael Foley https://issues.jboss.org/browse/KIALI-1843 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3225: ----------------------------------- Sprint: 2018 Week 42-44 > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3225: -------------------------------- Description: Issue spotted during DROOLS-3214, however probably not related. If decision table output data type is changed, the change is not reflected in the xml. Please follow my steps: - Create new DMN diagram - Add a decision node - Set the decision node top level expression as a decision table - Double click on Output header cell - Select boolean lets say - Save the diagram Check the source, there will be still stored string output data type, like below: {code:xml} <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> <dmn:text>input-1</dmn:text> </dmn:inputExpression> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> <dmn:text></dmn:text> </dmn:inputValues> </dmn:input> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> <dmn:text></dmn:text> </dmn:outputValues> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> <dmn:text></dmn:text> </dmn:defaultOutputEntry> </dmn:output> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> <dmn:text>"you are right"</dmn:text> </dmn:inputEntry> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> <dmn:text>true</dmn:text> </dmn:outputEntry> </dmn:rule> </dmn:decisionTable> </dmn:decision> {code} But the UI is like: !Screenshot from 2018-11-01 10-59-08.png|thumbnail! was: If decision table output data type is changed, the change is not reflected in the xml. Please follow my steps: - Create new DMN diagram - Add a decision node - Set the decision node top level expression as a decision table - Double click on Output header cell - Select boolean lets say - Save the diagram Check the source, there will be still stored string output data type, like below: {code:xml} <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> <dmn:text>input-1</dmn:text> </dmn:inputExpression> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> <dmn:text></dmn:text> </dmn:inputValues> </dmn:input> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> <dmn:text></dmn:text> </dmn:outputValues> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> <dmn:text></dmn:text> </dmn:defaultOutputEntry> </dmn:output> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> <dmn:text>"you are right"</dmn:text> </dmn:inputEntry> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> <dmn:text>true</dmn:text> </dmn:outputEntry> </dmn:rule> </dmn:decisionTable> </dmn:decision> {code} But the UI is like: !Screenshot from 2018-11-01 10-59-08.png|thumbnail! > [DMN Designer] Decision table output data type is not stored > ------------------------------------------------------------ > > Key: DROOLS-3225 > URL: https://issues.jboss.org/browse/DROOLS-3225 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2018-11-01 10-59-08.png > > > Issue spotted during DROOLS-3214, however probably not related. > If decision table output data type is changed, the change is not reflected in the xml. > Please follow my steps: > - Create new DMN diagram > - Add a decision node > - Set the decision node top level expression as a decision table > - Double click on Output header cell > - Select boolean lets say > - Save the diagram > Check the source, there will be still stored string output data type, like below: > {code:xml} > <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> > <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> > <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> > <dmn:text>input-1</dmn:text> > </dmn:inputExpression> > <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> > <dmn:text></dmn:text> > </dmn:inputValues> > </dmn:input> > <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> > <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> > <dmn:text></dmn:text> > </dmn:outputValues> > <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> > <dmn:text></dmn:text> > </dmn:defaultOutputEntry> > </dmn:output> > <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> > <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> > <dmn:text>"you are right"</dmn:text> > </dmn:inputEntry> > <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> > <dmn:text>true</dmn:text> > </dmn:outputEntry> > </dmn:rule> > </dmn:decisionTable> > </dmn:decision> > {code} > But the UI is like: > !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3225: ----------------------------------- Summary: [DMN Designer] Decision table output data type is not stored Key: DROOLS-3225 URL: https://issues.jboss.org/browse/DROOLS-3225 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-11-01 10-59-08.png If decision table output data type is changed, the change is not reflected in the xml. Please follow my steps: - Create new DMN diagram - Add a decision node - Set the decision node top level expression as a decision table - Double click on Output header cell - Select boolean lets say - Save the diagram Check the source, there will be still stored string output data type, like below: {code:xml} <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row"> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66"> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string"> <dmn:text>input-1</dmn:text> </dmn:inputExpression> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B"> <dmn:text></dmn:text> </dmn:inputValues> </dmn:input> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string"> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45"> <dmn:text></dmn:text> </dmn:outputValues> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string"> <dmn:text></dmn:text> </dmn:defaultOutputEntry> </dmn:output> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E"> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089"> <dmn:text>"you are right"</dmn:text> </dmn:inputEntry> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string"> <dmn:text>true</dmn:text> </dmn:outputEntry> </dmn:rule> </dmn:decisionTable> </dmn:decision> {code} But the UI is like: !Screenshot from 2018-11-01 10-59-08.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3224: -------------------------------- Description: Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded h2. Manaul acceptance test Autolayout is applied: - for asset linked above - for [^DMCommunity Challenge - March 2017.dmn] was: Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > h2. Manaul acceptance test > Autolayout is applied: > - for asset linked above > - for [^DMCommunity Challenge - March 2017.dmn] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3224: -------------------------------- Description: Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded h2. Manaul acceptance test Autolayout is applied: - for asset linked above - for [^DMCommunity Challenge - March 2017.dmn] - For 1.2 based assets was: Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded h2. Manaul acceptance test Autolayout is applied: - for asset linked above - for [^DMCommunity Challenge - March 2017.dmn] > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded > h2. Manaul acceptance test > Autolayout is applied: > - for asset linked above > - for [^DMCommunity Challenge - March 2017.dmn] > - For 1.2 based assets -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3224: -------------------------------- Workaround Description: (was: Save and reopen the DMN diagram before adding nodes.) > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3224) [DMN Designer] Autolayout is not applied for 1.1 based DMN models

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3224?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3224: -------------------------------- Workaround: (was: Workaround Exists) > [DMN Designer] Autolayout is not applied for 1.1 based DMN models > ----------------------------------------------------------------- > > Key: DROOLS-3224 > URL: https://issues.jboss.org/browse/DROOLS-3224 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn > > > Autolayout is not applied when [asset|https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-core...] uploaded -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2018