February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5062) [DMN Designer] Automatically correct node prefix/trailing space on import

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5062?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-5062: ------------------------------------------------ [~manstis] For files with the "error", I think we should warn the user and remove the trailing spaces. I don't see any value for the user in a trailing space in this context. Looks more like a typo. For new files, we should prevent user from creating nodes with trailing spaces. > [DMN Designer] Automatically correct node prefix/trailing space on import > ------------------------------------------------------------------------- > > Key: DROOLS-5062 > URL: https://issues.redhat.com/browse/DROOLS-5062 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Attachments: ItemDefinition-white-space.png > > > I understand [DROOLS-5017] has been re-purposed to allow Info and Warn level messages be displayed on Stunner Validation dialog. That is fine. > But, imho, an UX point is not being considered, where is necessary instead. > By the DMN spec, a node should not have a prefix/trailing space, as space insensitivity would mandate 1 trailing or 2 trailing spaces are simply ignored etc. > The engine is lenient to avoid this crashing the evaluation, but still is a bad designed model to persist the node name (DRGElement name and its corresponding variable name) with those extra spaces IMHO. > Further, I consider is just the Analyst which slipped a space. > In my perspective, the editor should just strip away the prefix/trailing space: > * While Importing a DMN model from file Upload > * -While editing a DRGElement and hitting OK to save its name- (See [DROOLS-5060|https://issues.redhat.com/browse/DROOLS-5060]) > For your consideration, thanks. > See [comment|https://issues.redhat.com/browse/DROOLS-5060?focusedCommentId=139...] on DROOLS-5060:- > {quote} > I'd like to move the other request ("While Importing a DMN model from file Upload") to a new JIRA for the following reason: > * It is an automated correction/cleanse > * We already have one automated correction (when layout information is missing or insufficient) > * We may, in the future, want to support other automated corrections > * I'd therefore like to consolidate the approach to how automated corrections are detected, ran and reported to the User. My initial opinion is that when opening (or importing or some other trigger to be determined) a DMN file we collect (probably via CDI discovery) all implementations of "Automated Fixers" (one of which if layout another is trim leading/trailing space etc). We then show the list of possible fixes to the User, they can select whatever they like and then we run them and save the file. Anyway, IMO, it's out of scope of this JIRA as it'd need some UX involvement. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-5056: ------------------------------------------------ The taxRate.dmn is a good file to reproduce this issue. I have success reproducing the issue with this file and using the zoom. Looks like is something related to the "virtual" position of the nodes on the screen and the real position. Using zoom while moving the nodes make the issue happens with more frequency. > [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned > ------------------------------------------------------------------------------- > > Key: DROOLS-5056 > URL: https://issues.redhat.com/browse/DROOLS-5056 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: issue.mp4, taxRate.dmn > > > Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again. > I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes. > I recorded a video with 2 minutes when the issue happens in the last seconds. > As it can be notice it takes lots of trials to reproduce the issue. > Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5056) [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5056?page=com.atlassian.jira.plug... ] Daniel José dos Santos updated DROOLS-5056: ------------------------------------------- Attachment: taxRate.dmn > [DMN Designer] Sometimes the nodes inside Decision Service are wrong positioned > ------------------------------------------------------------------------------- > > Key: DROOLS-5056 > URL: https://issues.redhat.com/browse/DROOLS-5056 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: issue.mp4, taxRate.dmn > > > Sometimes the nodes inside the Decision Service are positioned outside from the Decision Service when the .DMN is saved an open again. > I was unable to map exact when this happen, but I noticed that this happens depending on the changes you do in the position and size of the Decision Service and its inner nodes. > I recorded a video with 2 minutes when the issue happens in the last seconds. > As it can be notice it takes lots of trials to reproduce the issue. > Also I was unable to reproduce the issue in the Business Central, so I'm not sure if it is related to DMN Editor in VS Code or DMN Editor itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) Upgrade HAL to 3.2.6.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Description: This component upgrade contais bug fixes only. Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final was:Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final > Upgrade HAL to 3.2.6.Final > -------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > This component upgrade contais bug fixes only. > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) Upgrade HAL to 3.2.6.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12895) > Upgrade HAL to 3.2.6.Final > -------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) Upgrade HAL to 3.2.6.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Fix Version/s: 19.0.0.Beta3 (was: 19.0.0.Beta1) > Upgrade HAL to 3.2.6.Final > -------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) Upgrade HAL to 3.2.6.Final

by Harald Pehl (Jira)

Harald Pehl created WFLY-13091: ---------------------------------- Summary: Upgrade HAL to 3.2.6.Final Key: WFLY-13091 URL: https://issues.redhat.com/browse/WFLY-13091 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 19.0.0.Beta1 Diff: https://github.com/hal/console/compare/3.2.4.Final...3.2.5.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13091) Upgrade HAL to 3.2.6.Final

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-13091?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-13091: ------------------------------- Description: Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final (was: Diff: https://github.com/hal/console/compare/3.2.4.Final...3.2.5.Final) > Upgrade HAL to 3.2.6.Final > -------------------------- > > Key: WFLY-13091 > URL: https://issues.redhat.com/browse/WFLY-13091 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Major > Fix For: 19.0.0.Beta3 > > > Diff: https://github.com/hal/console/compare/3.2.5.Final...3.2.6.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13090) Enable compression on remoting globally for EJB calls

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13090?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-13090: ---------------------------------- Affects Version/s: 19.0.0.Beta2 > Enable compression on remoting globally for EJB calls > ----------------------------------------------------- > > Key: WFLY-13090 > URL: https://issues.redhat.com/browse/WFLY-13090 > Project: WildFly > Issue Type: Enhancement > Affects Versions: 19.0.0.Beta2 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13090) Enable compression on remoting globally for EJB calls

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13090?page=com.atlassian.jira.plugi... ] Tomasz Adamski updated WFLY-13090: ---------------------------------- Component/s: EJB > Enable compression on remoting globally for EJB calls > ----------------------------------------------------- > > Key: WFLY-13090 > URL: https://issues.redhat.com/browse/WFLY-13090 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 19.0.0.Beta2 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020