November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1745?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1745: ---------------------------- Fix Version/s: 1.11.0.CR3 (was: 1.11.0.CR2) > The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1745 > URL: https://issues.jboss.org/browse/ELY-1745 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR3 > > > The NPE is due to the following code: - > {noformat} > } else if (callback instanceof AvailableRealmsCallback) { > Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames(); > if (log.isTraceEnabled()) { > log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names)); > } > if (! names.isEmpty()) { > ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()])); > } > handleOne(callbacks, idx + 1); > {noformat} > If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4411) [DMN Designer] Included Models (Backlog)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4411?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4411: ------------------------------------ Description: This is an umbrella for all JIRAs related to the Included Models feature. (was: This is an umbrella for all JIRAs (target to 7.7) related to the Included Models feature.) > [DMN Designer] Included Models (Backlog) > ---------------------------------------- > > Key: DROOLS-4411 > URL: https://issues.jboss.org/browse/DROOLS-4411 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Included Models feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1906) Release WildFly Elytron 1.11.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1906?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1906. ----------------------------- Resolution: Done > Release WildFly Elytron 1.11.0.CR2 > ---------------------------------- > > Key: ELY-1906 > URL: https://issues.jboss.org/browse/ELY-1906 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4411) [DMN Designer] Included Models (Backlog)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4411?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4411: ------------------------------------ Summary: [DMN Designer] Included Models (Backlog) (was: [DMN Designer] Included Models (7.7)) > [DMN Designer] Included Models (Backlog) > ---------------------------------------- > > Key: DROOLS-4411 > URL: https://issues.jboss.org/browse/DROOLS-4411 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs (target to 7.7) related to the Included Models feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-74) Upgrade WildFly Elytron to 1.11.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-74?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELYWEB-74. ------------------------------ Resolution: Done > Upgrade WildFly Elytron to 1.11.0.CR2 > ------------------------------------- > > Key: ELYWEB-74 > URL: https://issues.jboss.org/browse/ELYWEB-74 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-75) Release Elytron Web 1.7.0.CR2

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELYWEB-75?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELYWEB-75. ------------------------------ Resolution: Done > Release Elytron Web 1.7.0.CR2 > ----------------------------- > > Key: ELYWEB-75 > URL: https://issues.jboss.org/browse/ELYWEB-75 > Project: Elytron Web > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3130) [DMN Designer] SugiyamaLayoutServiceTest

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3130?page=com.atlassian.jira.plugi... ] Daniel José dos Santos commented on DROOLS-3130: ------------------------------------------------ I was reviewing my pending JIRAS and found that this one is already done. I think we can close and mark as resolved. [~jomarko] It's done [https://github.com/kiegroup/kie-wb-common/blob/1da859aadeb5892d6e60272d6e...]. > [DMN Designer] SugiyamaLayoutServiceTest > ---------------------------------------- > > Key: DROOLS-3130 > URL: https://issues.jboss.org/browse/DROOLS-3130 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Create test class {{SugiyamaLayoutServiceTest}} for the [class|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3130) [DMN Designer] SugiyamaLayoutServiceTest

by Daniel José dos Santos (Jira)

[ https://issues.jboss.org/browse/DROOLS-3130?page=com.atlassian.jira.plugi... ] Daniel José dos Santos edited comment on DROOLS-3130 at 11/18/19 1:54 PM: -------------------------------------------------------------------------- I was reviewing my pending JIRAS and found that this one is already done. I think we can close and mark as resolved. [~jomarko] It's done [https://github.com/kiegroup/kie-wb-common/blob/1da859aadeb5892d6e60272d6e...] here. was (Author: dadossan): I was reviewing my pending JIRAS and found that this one is already done. I think we can close and mark as resolved. [~jomarko] It's done [https://github.com/kiegroup/kie-wb-common/blob/1da859aadeb5892d6e60272d6e...]. > [DMN Designer] SugiyamaLayoutServiceTest > ---------------------------------------- > > Key: DROOLS-3130 > URL: https://issues.jboss.org/browse/DROOLS-3130 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > Create test class {{SugiyamaLayoutServiceTest}} for the [class|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-269: ------------------------------ Description: Execute: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour. was: Execute: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Of course, colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour. > Colon in a header name doesn't show a warning > --------------------------------------------- > > Key: WFWIP-269 > URL: https://issues.jboss.org/browse/WFWIP-269 > Project: WildFly WIP > Issue Type: Bug > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Execute: > {code:java} > /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) > {code} > Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-269) Colon in a header name doesn't show a warning

by Tomas Terem (Jira)

[ https://issues.jboss.org/browse/WFWIP-269?page=com.atlassian.jira.plugin.... ] Tomas Terem updated WFWIP-269: ------------------------------ Description: Execute: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but users should at least see a warning describing this behaviour. was: Execute: {code:java} /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) {code} Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but I think that users should at least see a warning describing this behaviour. > Colon in a header name doesn't show a warning > --------------------------------------------- > > Key: WFWIP-269 > URL: https://issues.jboss.org/browse/WFWIP-269 > Project: WildFly WIP > Issue Type: Bug > Reporter: Tomas Terem > Assignee: Darran Lofthouse > Priority: Blocker > Labels: management > > Execute: > {code:java} > /core-service=management/management-interface=http-interface:write-attribute(name=constant-headers, value=[{path=/management, headers=[{name=A:B, value=C}]}]) > {code} > Reponse now has header 'A' with value 'B: C', but user wanted header 'A:B' with value 'C'. Colon can't be part of the header name, but users should at least see a warning describing this behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 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