November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4724?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4724: -------------------------------- Description: Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. However Error message is reported anyway to the user: !image-2019-11-04-19-39-01-113.png|thumbnail! This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression !image-2019-11-04-19-40-27-201.png|thumbnail! so the current behavior is not consistent across re-open of the editor. Let's revert this default. The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). Currently, the DMN Compiler will throw 1 Warning. Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). Currently, the DMN Validator schema check is not reporting any XSD violation. h2. Manual acceptance test Try to save default / empty - Lit. Expression - Context - Function - Decision Table - Relation - Invocation was: Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. However Error message is reported anyway to the user: !image-2019-11-04-19-39-01-113.png|thumbnail! This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression !image-2019-11-04-19-40-27-201.png|thumbnail! so the current behavior is not consistent across re-open of the editor. Let's revert this default. The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). Currently, the DMN Compiler will throw 1 Warning. Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). Currently, the DMN Validator schema check is not reporting any XSD violation. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.jboss.org/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > - Lit. Expression > - Context > - Function > - Decision Table > - Relation > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4724?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4724: -------------------------------- Tester: Jozef Marko Labels: drools-tools (was: ) > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.jboss.org/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12777: ------------------------------------- [~cfang] it seems like we are always hitting this during our Jakarta EE 8 TCK platform runs, so I think this should be a blocking issue. I'll update. CC: [~bstansberry2] > Stateful bean with @StatefulTimeout value -1 should not timeout or removed > -------------------------------------------------------------------------- > > Key: WFLY-12777 > URL: https://issues.jboss.org/browse/WFLY-12777 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Fix For: 19.0.0.Beta1 > > > Stateful bean with @StatefulTimeout value -1 should not timeout or removed. > A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. > {code:java} > @Stateful > @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) > @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) > @Local(StatefulTimeoutIF.class) > public class Minus1TimeoutBean { > ... > } > {code} > Or the stateful bean timeout can be configured with ejb-jar.xml: > {code:xml} > <session> > <ejb-name>xx</ejb-name> > <business-local>xx</business-local> > <ejb-class>xx</ejb-class> > <session-type>Stateful</session-type> > <stateful-timeout> > <timeout>-1</timeout> > <unit>Days</unit> > </stateful-timeout> > <concurrency-management-type>Container</concurrency-management-type> > </session> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12777) Stateful bean with @StatefulTimeout value -1 should not timeout or removed

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12777?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-12777: -------------------------------- Priority: Blocker (was: Major) > Stateful bean with @StatefulTimeout value -1 should not timeout or removed > -------------------------------------------------------------------------- > > Key: WFLY-12777 > URL: https://issues.jboss.org/browse/WFLY-12777 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 19.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Blocker > Fix For: 19.0.0.Beta1 > > > Stateful bean with @StatefulTimeout value -1 should not timeout or removed. > A value of -1 means the bean will never be removed due to timeout. When running with the latest WildFly snapshot (2019-11-11), such a stateful bean was unexpectedly timed out and removed. > {code:java} > @Stateful > @StatefulTimeout(value = -1, unit=TimeUnit.DAYS) > @AccessTimeout(value=StatefulTimeoutIF.TIMEOUT_DAYS, unit=TimeUnit.DAYS) > @Local(StatefulTimeoutIF.class) > public class Minus1TimeoutBean { > ... > } > {code} > Or the stateful bean timeout can be configured with ejb-jar.xml: > {code:xml} > <session> > <ejb-name>xx</ejb-name> > <business-local>xx</business-local> > <ejb-class>xx</ejb-class> > <session-type>Stateful</session-type> > <stateful-timeout> > <timeout>-1</timeout> > <unit>Days</unit> > </stateful-timeout> > <concurrency-management-type>Container</concurrency-management-type> > </session> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4796) Stunner - Keep Properties panel state during asset switching

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4796?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4796: -------------------------------- Description: Issue was found during DROOLS-4772 [review|https://github.com/kiegroup/kie-wb-common/pull/3021#pullrequestrev...]. If user switch between stunner assets (DMN, BPMN), the properties panel is always collapsed after returning to the asset. Even if it was expanded before leaving the editor. See the attached video. (was: To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. h4. Acceptance criteria After DMN editor is opened, Properties panel is opened immediately without any interaction required. It is possible to close and open it back using "Properties panel button". ) > Stunner - Keep Properties panel state during asset switching > ------------------------------------------------------------ > > Key: DROOLS-4796 > URL: https://issues.jboss.org/browse/DROOLS-4796 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: switch-dmns.webm > > > Issue was found during DROOLS-4772 [review|https://github.com/kiegroup/kie-wb-common/pull/3021#pullrequestrev...]. If user switch between stunner assets (DMN, BPMN), the properties panel is always collapsed after returning to the asset. Even if it was expanded before leaving the editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4796) Stunner - Keep Properties panel state during asset switching

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4796?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4796: -------------------------------- Issue Type: Bug (was: Task) > Stunner - Keep Properties panel state during asset switching > ------------------------------------------------------------ > > Key: DROOLS-4796 > URL: https://issues.jboss.org/browse/DROOLS-4796 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: switch-dmns.webm > > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. > h4. Acceptance criteria > After DMN editor is opened, Properties panel is opened immediately without any interaction required. > It is possible to close and open it back using "Properties panel button". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4796) Stunner - Keep Properties panel state during asset switching

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4796?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4796: -------------------------------- Git Pull Request: (was: https://github.com/kiegroup/kie-wb-common/pull/3021) > Stunner - Keep Properties panel state during asset switching > ------------------------------------------------------------ > > Key: DROOLS-4796 > URL: https://issues.jboss.org/browse/DROOLS-4796 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: switch-dmns.webm > > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. > h4. Acceptance criteria > After DMN editor is opened, Properties panel is opened immediately without any interaction required. > It is possible to close and open it back using "Properties panel button". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4796) Stunner - Keep Properties panel state during asset switching

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4796?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4796: -------------------------------- Summary: Stunner - Keep Properties panel state during asset switching (was: [DMN Designer] Keep Properties panel state during asset switching) > Stunner - Keep Properties panel state during asset switching > ------------------------------------------------------------ > > Key: DROOLS-4796 > URL: https://issues.jboss.org/browse/DROOLS-4796 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: switch-dmns.webm > > > To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. > h4. Acceptance criteria > After DMN editor is opened, Properties panel is opened immediately without any interaction required. > It is possible to close and open it back using "Properties panel button". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4796) [DMN Designer] Keep Properties panel state during asset switching

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4796: ----------------------------------- Summary: [DMN Designer] Keep Properties panel state during asset switching Key: DROOLS-4796 URL: https://issues.jboss.org/browse/DROOLS-4796 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.29.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: switch-dmns.webm To improve user experience and let users locate Properties panel more easily, it should be opened by default when opening DMN editor. h4. Acceptance criteria After DMN editor is opened, Properties panel is opened immediately without any interaction required. It is possible to close and open it back using "Properties panel button". -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12816) licenses should be provisioned with galleon layers

by Jean Francois Denise (Jira)

Jean Francois Denise created WFLY-12816: ------------------------------------------- Summary: licenses should be provisioned with galleon layers Key: WFLY-12816 URL: https://issues.jboss.org/browse/WFLY-12816 Project: WildFly Issue Type: Bug Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise The license files are not provisioned when galleon provision a server from layers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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