March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Donato Marrazzo (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Donato Marrazzo commented on DROOLS-3784: ----------------------------------------- [~uxdlc] I'm not convinced that this is a great benefit. If I understood correctly the context menu is accessible via right click that does not change much the visibility of the feature. Moreover, it does not change the number of click / action to add a nested element: 1. save the structure node 2. add nested element 3. save nested element 4. add nested element 5. save nested element etc Semantically, it's even incorrect! Why should I save something that is not complete? The structure can be saved only when it is completed with all nested element. When I add a new nested element the structure should be saved again! The logical sequence of action is: 1. create the structure node 2. add the nested element 3. add the nested element 4. (repeat for all nested elements) 5. save the structure node I believe that in terms of graphical metaphor the structure should start with a "nested placeholder" with a label "add nested element", when the user clicks the placeholder the new element appears and the placehoder shift down. Look at the attached screenshot. !nested.png|thumbnail! > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Donato Marrazzo (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Donato Marrazzo updated DROOLS-3784: ------------------------------------ Attachment: nested.png > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1712) Enhanced Audit Logging - RFC support and reliability/speed customization

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1712?page=com.atlassian.jira.plugin.s... ] Justin Cook updated ELY-1712: ----------------------------- Description: This RFE for Enhanced Audit Logging in WildFly Elytron is for: * RFC5424 Support * RFC3164 Support * "hostname" attribute (see https://access.redhat.com/support/cases/#/case/02188481) * Reliability vs Speed Customization was: Something along the lines of: - * More audit events * Custom Filters * Advanced routing configuration based on type / priority / additional criteria. * QOS type optimisations, i.e. reliability of logging vs performance. We are also missing support for: - * RFC5424 * RFC3164 * User formated string * "hostname" attribute (see https://access.redhat.com/support/cases/#/case/02188481) > Enhanced Audit Logging - RFC support and reliability/speed customization > ------------------------------------------------------------------------ > > Key: ELY-1712 > URL: https://issues.jboss.org/browse/ELY-1712 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > > This RFE for Enhanced Audit Logging in WildFly Elytron is for: > * RFC5424 Support > * RFC3164 Support > * "hostname" attribute (see https://access.redhat.com/support/cases/#/case/02188481) > * Reliability vs Speed Customization -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1712) Enhanced Audit Logging - RFC support and reliability/speed customization

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1712?page=com.atlassian.jira.plugin.s... ] Justin Cook updated ELY-1712: ----------------------------- Summary: Enhanced Audit Logging - RFC support and reliability/speed customization (was: Enhanced Audit Logging) > Enhanced Audit Logging - RFC support and reliability/speed customization > ------------------------------------------------------------------------ > > Key: ELY-1712 > URL: https://issues.jboss.org/browse/ELY-1712 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Justin Cook > Assignee: Justin Cook > Priority: Major > > Something along the lines of: - > * More audit events > * Custom Filters > * Advanced routing configuration based on type / priority / additional criteria. > * QOS type optimisations, i.e. reliability of logging vs performance. > We are also missing support for: - > * RFC5424 > * RFC3164 > * User formated string > * "hostname" attribute (see https://access.redhat.com/support/cases/#/case/02188481) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11897) SFSB expiration failures cause memory leak

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-11897: -------------------------------- Priority: Critical (was: Major) > SFSB expiration failures cause memory leak > ------------------------------------------ > > Key: WFLY-11897 > URL: https://issues.jboss.org/browse/WFLY-11897 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Critical > Attachments: WFLY-11897.btm, test.ear > > > There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11836) Expand ha-singleton-service to demonstrate Singleton service election listeners

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11836?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-11836: --------------------------------------- We have to wait for release containing EAP7-1115/WFLY-11098 i.e. 17.0.0.Beta1. > Expand ha-singleton-service to demonstrate Singleton service election listeners > ------------------------------------------------------------------------------- > > Key: WFLY-11836 > URL: https://issues.jboss.org/browse/WFLY-11836 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Demonstrate feature implemented in EAP7-1115. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11821) Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-11821?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-11821: --------------------------------------- Merged. > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11821 > URL: https://issues.jboss.org/browse/WFLY-11821 > Project: WildFly > Issue Type: Task > Components: Clustering, Quickstarts > Affects Versions: 16.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 17.0.0.Beta1 > > > Remove ha-singleton-service/with-backups quickstart since it's no longer supported without deprecated API usage. This is due to MSC-203. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11900?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11900: ------------------------------------- You might also want to upgrade to a more recent version of WildFly (e.g. 16.0.0.Final). There were a number of improvements made to improve the JGroups merging process. > Wildfly 14 + JGroups + Singleton Cluster Not Working > ---------------------------------------------------- > > Key: WFLY-11900 > URL: https://issues.jboss.org/browse/WFLY-11900 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Bhavesh Kharwa > Assignee: Paul Ferraro > Priority: Major > Fix For: 14.0.0.Final > > > Singleton cluster is not working if starts both servers at same time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11900?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11900: ------------------------------------- [~bhavesh.rkharwa] Please attach server logs from both machines so that we can tell what is preventing your clusters from merging. In general, singleton services are only as reliable as the cluster on which they run. To ensure that you singleton services do not start while your cluster is partitioned (or, in your case, not yet merged), you should build your singleton service such that it requires a quorum of 2. > Wildfly 14 + JGroups + Singleton Cluster Not Working > ---------------------------------------------------- > > Key: WFLY-11900 > URL: https://issues.jboss.org/browse/WFLY-11900 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Bhavesh Kharwa > Assignee: Paul Ferraro > Priority: Major > Fix For: 14.0.0.Final > > > Singleton cluster is not working if starts both servers at same time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4362) Make the certificate authority used by a certificate-authority-account configurable

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4362?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4362: ---------------------------------------- Assignee: Diana Vilkolakova > Make the certificate authority used by a certificate-authority-account configurable > ----------------------------------------------------------------------------------- > > Key: WFCORE-4362 > URL: https://issues.jboss.org/browse/WFCORE-4362 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Diana Vilkolakova > Priority: Major > > Currently, Let's Encrypt (https://acme-v02.api.letsencrypt.org/directory) is the only certificate authority that can be used by a {{certificate-authority-account}}. In the future, if/when other certificate authorities implement the server side of the ACME protocol, this will need to be configurable. In addition, making this configurable would also allow local Let's Encrypt server instances to be used for testing purposes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019