October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3203: -------------------------------------- Summary: [DMN Designer] Runtime issues Key: DROOLS-3203 URL: https://issues.jboss.org/browse/DROOLS-3203 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3189) Add info tip to "Collection" switch

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3189?page=com.atlassian.jira.plugi... ] Guilherme Carreiro commented on DROOLS-3189: -------------------------------------------- [~stetson.robinson] [~uxdlc] The DMN definition for the {{isCollection}} field is: {quote}Setting this flag to true indicates that the actual values defined by this ItemDefinition are collections of allowed values. The default is false.{quote} Thanks. > Add info tip to "Collection" switch > ----------------------------------- > > Key: DROOLS-3189 > URL: https://issues.jboss.org/browse/DROOLS-3189 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Minor > Labels: UX, UXTeam > > User could benefit from some on screen info tip help (i) for the Collection (yes/no) option. This jira is to create the copy required for the info tip bubble. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3202) [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a equal to a built in Data Type type

by Guilherme Carreiro (Jira)

Guilherme Carreiro created DROOLS-3202: ------------------------------------------ Summary: [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a equal to a built in Data Type type Key: DROOLS-3202 URL: https://issues.jboss.org/browse/DROOLS-3202 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Carreiro Assignee: Guilherme Carreiro The Data Type dialog cannot allow the following data type names: - number - string - boolean - days and time duration - years and months duration - time - date and time - any - date - context A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Brad Maxwell (Jira)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Brad Maxwell edited comment on WFLY-6573 at 10/26/18 1:47 PM: -------------------------------------------------------------- At a simplistic level, this is like changing a system property at runtime, but in reality everything that is configured with these properties has to be restarted, such as datasources, ldap, etc... Which would not be recommended to do at runtime when these resources are likely being actively used and changing without restart where it basically restarts everything using it seems like it does not gain that much. Datasources and ldap configuration are a couple of areas which would need to be investigated to restart and anything that uses those. was (Author: bmaxwell): At a simplistic level, this is like changing a system property at runtime, but in reality everything that is configured with these properties has to be restarted, such as datasources, ldap, etc... Which would not be recommended to do at runtime when these resources are likely being actively used and changing without restart where it basically restarts everything using it seems like it does not gain that much. > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Priority: Major > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-6573: ---------------------------------------- [~bmaxwell] That is why I think we need to start by identifying resources that make use of credentials from the credential store and prioritise them - automatic service restarts is a complete non-starter as we effectively restart the majority of the app server (including deployments) just by updating a credential. The approach I think we will need to follow is some form of notification that a credential has been updated, selected services can then choose to respond to that notification in a suitable way. Each of these services will then require it's own analysis and implementation hence the prioritisation. As an example if we have pool of functioning JDBC connection we may choose to continue to use them as long as they remain valid, new connections would make use of the new credential. But this will require specific integration into our JDBC connection handling rather than being a generic top level idea. > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Priority: Major > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Brad Maxwell (Jira)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Brad Maxwell commented on WFLY-6573: ------------------------------------ At a simplistic level, this is like changing a system property at runtime, but in reality everything that is configured with these properties has to be restarted, such as datasources, ldap, etc... Which would not be recommended to do at runtime when these resources are likely being actively used and changing without restart where it basically restarts everything using it seems like it does not gain that much. > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Priority: Major > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3151: ------------------------------------- [~danielezonca] In your example above , the values "Scenario Text" and "Given 2" are also placeholder text - yes? At least until the actual values are input. Would they also pick up whatever style treatment that you and [~bdellasc] decide on? > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Fix For: 7.14.0.Final > > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, Screenshot from 2018-10-26 18-25-59.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Brian Dellascio (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Brian Dellascio commented on DROOLS-3151: ----------------------------------------- [~danielezonca] I checked using an accessibility/contrast tool, and I'd be reluctant to go any lighter than #757575. Below that level, most contrast standards would fail it. I think the use of italics and #757575 would be sufficient to show it's placeholder text. Here's the contrast checker tool I was referring to: https://webaim.org/resources/contrastchecker/ Thanks for asking! > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Fix For: 7.14.0.Final > > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, Screenshot from 2018-10-26 18-25-59.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3151: --------------------------------------- [~bdellasc] No problem :) Another question, I'm updating the colors to align to your proposal and I would like to know what do you think to have two different colors for actual text and placeholders (like in general HTML5) !Screenshot from 2018-10-26 18-25-59.png|thumbnail! In the screenshot I used the same color of the grid for the placeholder but maybe it is a bit too light. WDYT? Let me know if you prefer to have the same color and only _italic_ to identify placeholder of also a different color. > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Fix For: 7.14.0.Final > > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, Screenshot from 2018-10-26 18-25-59.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3151) [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3151?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3151: ---------------------------------- Attachment: Screenshot from 2018-10-26 18-25-59.png > [DMN Designer] Decision Table: Improve contrast of Input- and OutputClause columns > ---------------------------------------------------------------------------------- > > Key: DROOLS-3151 > URL: https://issues.jboss.org/browse/DROOLS-3151 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: VisualDesign, drools-tools > Fix For: 7.14.0.Final > > Attachments: DROOLS-3151-DMN.png, DROOLS-3151-GDT.png, GDT.png, Screenshot from 2018-10-26 18-25-59.png, dtable-column-colours.png > > > [~tirelli] requested greater visual contrast between {{InputClause}} and {{OutputClause}} columns. > {quote} > this is way too subtle, to be honest... can we get colours that are a bit more distinguishable? > {quote} > See the attached screenshot. > Additional note for clarity, goal is to: clearly differentiate between different blocks of columns (decision table: input column, output column plus possibly a third "general" type.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018