May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3731: ------------------------------------------- Thanks for the clarification [~tirelli]. Question [~roger.martinez], doesn't Stunner already handle something like #2 (validation errors display)? > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, download (1).png, download.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3731: --------------------------------------- [~uxdlc] just to be clear, there are two scenarios: 1. only a single test is executed, in which case we can show pop-overs with the errors and such, including expected and actual values on the decisions 2. several tests are executed, in which case the best we can do is show colour coded nodes (e.g.: green means covered and always succeeded, red means covered and always failed, yellow means covered and some success/some failures, grey means not covered). Colours are just examples, feel free to suggest. The pop-overs would not be able to display any meaningful information, other than what the colours mean. > DMN UX - More info overlaid on models. > -------------------------------------- > > Key: DROOLS-3731 > URL: https://issues.jboss.org/browse/DROOLS-3731 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-05-29 at 2.49.21 PM.png, download (1).png, download.png > > > As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression. > Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12138) Microprofile REST Client 1.3 implementation

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12138?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-12138: ----------------------------------- Summary: Microprofile REST Client 1.3 implementation (was: Microprofile REST Client 1.3.1 implementation) > Microprofile REST Client 1.3 implementation > ------------------------------------------- > > Key: WFLY-12138 > URL: https://issues.jboss.org/browse/WFLY-12138 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 18.0.0.Beta1 > > > Provide an implementation of the Microprofile RestClient specification 1.3.1. > Specification: https://github.com/eclipse/microprofile-rest-client/releases/tag/1.3.1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12138) Microprofile REST Client 1.3 implementation

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12138?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-12138: ----------------------------------- Description: Provide an implementation of the Microprofile RestClient specification 1.3. Latest available specification: https://github.com/eclipse/microprofile-rest-client/releases/tag/1.3.2 was: Provide an implementation of the Microprofile RestClient specification 1.3.1. Specification: https://github.com/eclipse/microprofile-rest-client/releases/tag/1.3.1 > Microprofile REST Client 1.3 implementation > ------------------------------------------- > > Key: WFLY-12138 > URL: https://issues.jboss.org/browse/WFLY-12138 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 18.0.0.Beta1 > > > Provide an implementation of the Microprofile RestClient specification 1.3. > Latest available specification: https://github.com/eclipse/microprofile-rest-client/releases/tag/1.3.2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12151) Odd error message when trying to add a resources if the host is not selected

by James Perkins (Jira)

James Perkins created WFLY-12151: ------------------------------------ Summary: Odd error message when trying to add a resources if the host is not selected Key: WFLY-12151 URL: https://issues.jboss.org/browse/WFLY-12151 Project: WildFly Issue Type: Bug Components: Web Console Reporter: James Perkins Assignee: Harald Pehl Attempting to add an access log, HTTP invoke or Single Sign On resource when the host is not selected host under {{subsystem=undertow/server=default-server/}} via the web console fails with: {code} Failed to add singleton resource Access Log, cause: "WFLYCTL0175: Resource [ (\"subsystem\" => \"undertow\"), (\"server\" => \"default-server\"), (\"host\" => \"_blank\") ] does not exist; a resource at address [ (\"subsystem\" => \"undertow\"), (\"server\" => \"default-server\"), (\"host\" => \"_blank\"), (\"setting\" => \"access-log\") ] cannot be created until all ancestor resources have been added" {code} Once selected, then deselected the "Add" button is no longer an option so the resource an't be attempted to be added on a non-selected host. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-769) Install and Build Job doesn't support OAuth Deployment

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-769: --------------------------------------------- Summary: Install and Build Job doesn't support OAuth Deployment Key: SWSQE-769 URL: https://issues.jboss.org/browse/SWSQE-769 Project: Kiali QE Issue Type: Task Reporter: Guilherme Baufaker Rêgo Kiali-on-openshift and install-build-kiali only use Login strategy. It needs to support the OAuth method which is standard for OCP4 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4302) SNI wildcard mappings match multiple level of subdomain

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4302?page=com.atlassian.jira.plugi... ] Diana Vilkolakova edited comment on WFCORE-4302 at 5/31/19 11:16 AM: --------------------------------------------------------------------- [~dlofthouse] This relates to my recent changes in such a way, that this complex regex [~jstourac] used in the comment above : "[^.]*\\.example\\.com" is not allowed now. Only regexes with quare brackets, dots, question marks and asterisks are allowed. The character '^' will not pass and nothing except dot can be escaped, so eg. \W for nonword characters is also not allowed. I don't think such complex regexes would be used by users, but as [~dlofthouse] suggested, we will keep current validation and look for user comments / bug reports. Validation for all possible regexes seems unnecessary and in such case it would make sense to remove the validation completely. was (Author: dvilkola): [~dlofthouse] This relates to my recent changes in such a way, that this complex regex [~jstourac] used in the comment above : "[^.]*\\.example\\.com" is not allowed now. Only regexes with quare brackets, dots, question marks and asterisks are allowed. The character '^' will not pass and nothing except dot can be escaped, so eg. \W for nonword characters is also not allowed. I don't think such complex regexes would be used by users, but as [~dlofthouse] suggested, we will keep current validation and look for user comments / bug reports. Validation for all possible regexes seems unnecessary. > SNI wildcard mappings match multiple level of subdomain > ------------------------------------------------------- > > Key: WFCORE-4302 > URL: https://issues.jboss.org/browse/WFCORE-4302 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 7.0.0.Final > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Pavel Jelinek > Assignee: Martin Mazanek > Priority: Major > Labels: SNI > > Based on the [text from analasys|https://github.com/wildfly/wildfly-proposals/blob/master/securit...]: > {quote} > Wildcard names use * as a wildcard, and can only be used to match a single level of subdomain in much the same way as with wildcard certificates. > {quote} > As such, in case I have configured SNI mapping for: > {code} > .*\\.example\\.com > {code} > I expect that this mapping is selected for any single level of subdomain of example.com although, in case of any extra subdomain, this mapping is not utilized. In other words, following hostnames should match: > {code} > test.example.com > another-test.example.com > {code} > although following should not be matched and default server-ssl-context shall be used instead: > {code} > two-sublevel.one-sublevel.example.com > {code} > Current behaviour also matches also 'two-sublevel.one-sublevel.example.com'. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4302) SNI wildcard mappings match multiple level of subdomain

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4302?page=com.atlassian.jira.plugi... ] Diana Vilkolakova edited comment on WFCORE-4302 at 5/31/19 11:14 AM: --------------------------------------------------------------------- [~dlofthouse] This relates to my recent changes in such a way, that this complex regex [~jstourac] used in the comment above : "[^.]*\\.example\\.com" is not allowed now. Only regexes with quare brackets, dots, question marks and asterisks are allowed. The character '^' will not pass and nothing except dot can be escaped, so eg. \W for nonword characters is also not allowed. I don't think such complex regexes would be used by users, but as [~dlofthouse] suggested, we will keep current validation and look for user comments / bug reports. Validation for all possible regexes seems unnecessary. was (Author: dvilkola): [~dlofthouse] This relates to my recent changes in such a way, that this complex regex [~jstourac] used in the comment above : "[^.]*\\.example\\.com" is not allowed now. Only regexes with quare brackets, dots, question marks and asterisks are allowed. The character '^' will not pass and nothing except dot can be escaped, so eg. \W for nonword characters is also not allowed. I don't think such complex regexes would be used by users, but as [~dlofthouse] suggested, we will keep current validation and look for user comments / bug reports. > SNI wildcard mappings match multiple level of subdomain > ------------------------------------------------------- > > Key: WFCORE-4302 > URL: https://issues.jboss.org/browse/WFCORE-4302 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 7.0.0.Final > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Pavel Jelinek > Assignee: Martin Mazanek > Priority: Major > Labels: SNI > > Based on the [text from analasys|https://github.com/wildfly/wildfly-proposals/blob/master/securit...]: > {quote} > Wildcard names use * as a wildcard, and can only be used to match a single level of subdomain in much the same way as with wildcard certificates. > {quote} > As such, in case I have configured SNI mapping for: > {code} > .*\\.example\\.com > {code} > I expect that this mapping is selected for any single level of subdomain of example.com although, in case of any extra subdomain, this mapping is not utilized. In other words, following hostnames should match: > {code} > test.example.com > another-test.example.com > {code} > although following should not be matched and default server-ssl-context shall be used instead: > {code} > two-sublevel.one-sublevel.example.com > {code} > Current behaviour also matches also 'two-sublevel.one-sublevel.example.com'. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4302) SNI wildcard mappings match multiple level of subdomain

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4302?page=com.atlassian.jira.plugi... ] Diana Vilkolakova commented on WFCORE-4302: ------------------------------------------- [~dlofthouse] This relates to my recent changes in such a way, that this complex regex [~jstourac] used in the comment above : "[^.]*\\.example\\.com" is not allowed now. Only regexes with quare brackets, dots, question marks and asterisks are allowed. The character '^' will not pass and nothing except dot can be escaped, so eg. \W for nonword characters is also not allowed. I don't think such complex regexes would be used by users, but as [~dlofthouse] suggested, we will keep current validation and look for user comments / bug reports. > SNI wildcard mappings match multiple level of subdomain > ------------------------------------------------------- > > Key: WFCORE-4302 > URL: https://issues.jboss.org/browse/WFCORE-4302 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 7.0.0.Final > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Pavel Jelinek > Assignee: Martin Mazanek > Priority: Major > Labels: SNI > > Based on the [text from analasys|https://github.com/wildfly/wildfly-proposals/blob/master/securit...]: > {quote} > Wildcard names use * as a wildcard, and can only be used to match a single level of subdomain in much the same way as with wildcard certificates. > {quote} > As such, in case I have configured SNI mapping for: > {code} > .*\\.example\\.com > {code} > I expect that this mapping is selected for any single level of subdomain of example.com although, in case of any extra subdomain, this mapping is not utilized. In other words, following hostnames should match: > {code} > test.example.com > another-test.example.com > {code} > although following should not be matched and default server-ssl-context shall be used instead: > {code} > two-sublevel.one-sublevel.example.com > {code} > Current behaviour also matches also 'two-sublevel.one-sublevel.example.com'. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12150) Change AttributeDefinitions that have a default value and are set as required

by Michal Petrov (Jira)

Michal Petrov created WFLY-12150: ------------------------------------ Summary: Change AttributeDefinitions that have a default value and are set as required Key: WFLY-12150 URL: https://issues.jboss.org/browse/WFLY-12150 Project: WildFly Issue Type: Enhancement Reporter: Michal Petrov Assignee: Michal Petrov Per [WFCORE-2252], it doesn't make sense for an AttributeDefinition to provide a default value if it set as required. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 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 May 2019