May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1906) Guided Rule Editor: Frozen Conditions and Actions should have a human readable text

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1906?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1906: ----------------------------------- Sprint: 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-20 (was: 2018 Week 15-16, 2018 Week 17-18) > Guided Rule Editor: Frozen Conditions and Actions should have a human readable text > ----------------------------------------------------------------------------------- > > Key: DROOLS-1906 > URL: https://issues.jboss.org/browse/DROOLS-1906 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor, Guided Template Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Minor > Attachments: freeze.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1946: ----------------------------------- Sprint: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-20 (was: 2017 Week 24-25, 2017 Week 26-27, 2017 Week 28-29, 2017 Week 30-31, 2017 Week 32-33, 2017 Week 34-35, 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02, 2018 Week 03-04, 2018 Week 05-06, 2018 Week 07-08, 2018 Week 09-10, 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18) > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.8.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2538) [DMN Designer] Save throws NPE

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2538?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2538: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-20 (was: 2018 Week 17-18) > [DMN Designer] Save throws NPE > ------------------------------ > > Key: DROOLS-2538 > URL: https://issues.jboss.org/browse/DROOLS-2538 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Attachments: null-pointer.png > > > Save of the diagram throws NPE, see the attachment. > h2. PR Acceptance test > - Check saving of empty diagram (/) > - Check saving of diagram containing (/) > -- Nodes > -- Nodes and connections > -- Non empty decision nodes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2274) "?" special variable support

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2274?page=com.atlassian.jira.plugi... ] Kris Verlaenen reopened DROOLS-2274: ------------------------------------ Reopening as sub-task is not complete yet (blocking sprint from being closed). > "?" special variable support > ---------------------------- > > Key: DROOLS-2274 > URL: https://issues.jboss.org/browse/DROOLS-2274 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Fedor Gavrilov > Assignee: Edson Tirelli > Fix For: 7.8.0.Final > > Attachments: DMN12-71_proposal_v3.docx > > > DMN 1.2 includes the support for extended unary tests that are basically expression in decision table cells that include the special variable '?'. See attached proposal. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3849) CLI cursor disorder for Up and Down Arrow

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3849?page=com.atlassian.jira.plugi... ] Ingo Weiss reassigned WFCORE-3849: ---------------------------------- Assignee: Ingo Weiss (was: Jean-Francois Denise) > CLI cursor disorder for Up and Down Arrow > ----------------------------------------- > > Key: WFCORE-3849 > URL: https://issues.jboss.org/browse/WFCORE-3849 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 5.0.0.Beta2 > Reporter: Chao Wang > Assignee: Ingo Weiss > Priority: Critical > > Connect to CLI and click keyboard up and down arrows (assuming there is history commands there). Terminal cursor moves up in a confused manner. This happens since WFCORE Beta 1 version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-82) remove deprecated API

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-82?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-82. ----------------------------- Resolution: Done > remove deprecated API > --------------------- > > Key: AG-82 > URL: https://issues.jboss.org/browse/AG-82 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 0.5 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.6 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3852) Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3852?page=com.atlassian.jira.plugi... ] Jan Kalina reassigned WFCORE-3852: ---------------------------------- Assignee: (was: Jan Kalina) > Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker > -------------------------------------------------------------------------------- > > Key: WFCORE-3852 > URL: https://issues.jboss.org/browse/WFCORE-3852 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta1 > Reporter: Jan Kalina > Labels: transformers > > When defined ObjectFieldsRejectAttributeChecker (or ListRejectAttributeChecker or their combination) in transformers, the error message is missleading - points to the complex attribute instead of individual subattributes: > {code} > WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ], > \"operation\" => \"add\", > \"principal-query\" => [{ > \"data-source\" => \"ExampleDS\", > \"sql\" => \"SEL\", > \"scram-mapper\" => { > \"iteration-count-index\" => \"1\", > \"password-index\" => \"2\", > \"salt-index\" => \"5\", > \"hash-encoding\" => \"base64\" // this attribute is not backward compatible > } > }], > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"658c12cc-9501-47d0-bf24-aa11079e444a\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => -1163262107 > } > } at resource [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ] to subsystem 'elytron' model version '2.0.0' -- attributes [principal-query] WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] > {code} > The error message should contain something like {{[principal-query[0].scram-mapper.hash-encoding]}} instead of {{[principal-query]}}. > The error message is misleading, as the attribute {{[principal-query]}} HAS TO be defined - only the {{hash-encoding}} must not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3852) Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3852?page=com.atlassian.jira.plugi... ] Jan Kalina commented on WFCORE-3852: ------------------------------------ As the fix would required changing checker interface, unassigning. > Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker > -------------------------------------------------------------------------------- > > Key: WFCORE-3852 > URL: https://issues.jboss.org/browse/WFCORE-3852 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: transformers > > When defined ObjectFieldsRejectAttributeChecker (or ListRejectAttributeChecker or their combination) in transformers, the error message is missleading - points to the complex attribute instead of individual subattributes: > {code} > WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ], > \"operation\" => \"add\", > \"principal-query\" => [{ > \"data-source\" => \"ExampleDS\", > \"sql\" => \"SEL\", > \"scram-mapper\" => { > \"iteration-count-index\" => \"1\", > \"password-index\" => \"2\", > \"salt-index\" => \"5\", > \"hash-encoding\" => \"base64\" // this attribute is not backward compatible > } > }], > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"658c12cc-9501-47d0-bf24-aa11079e444a\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => -1163262107 > } > } at resource [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ] to subsystem 'elytron' model version '2.0.0' -- attributes [principal-query] WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] > {code} > The error message should contain something like {{[principal-query[0].scram-mapper.hash-encoding]}} instead of {{[principal-query]}}. > The error message is misleading, as the attribute {{[principal-query]}} HAS TO be defined - only the {{hash-encoding}} must not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3852) Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3852?page=com.atlassian.jira.plugi... ] Jan Kalina commented on WFCORE-3852: ------------------------------------ Edit: it is more complicated than I has think - current RejectAttributeChecker interface does not allow to find which part of complex attribute has failed - getRejectionLogMessage() and getRejectionLogMessageId() have no info about failed value - cannot determine which field has failed and provide appropriate error message. There is also possibility the error message will be more missleading then described above - when two different things are tested on fields of one complex attribute, the error message for first tested field will be thrown regardless which of them has failed :/ > Incomplete attribute name in error message of ObjectFieldsRejectAttributeChecker > -------------------------------------------------------------------------------- > > Key: WFCORE-3852 > URL: https://issues.jboss.org/browse/WFCORE-3852 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta1 > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: transformers > > When defined ObjectFieldsRejectAttributeChecker (or ListRejectAttributeChecker or their combination) in transformers, the error message is missleading - points to the complex attribute instead of individual subattributes: > {code} > WFLYCTL0297: Transforming operation { > \"address\" => [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ], > \"operation\" => \"add\", > \"principal-query\" => [{ > \"data-source\" => \"ExampleDS\", > \"sql\" => \"SEL\", > \"scram-mapper\" => { > \"iteration-count-index\" => \"1\", > \"password-index\" => \"2\", > \"salt-index\" => \"5\", > \"hash-encoding\" => \"base64\" // this attribute is not backward compatible > } > }], > \"operation-headers\" => { > \"caller-type\" => \"user\", > \"access-mechanism\" => \"NATIVE\", > \"domain-uuid\" => \"658c12cc-9501-47d0-bf24-aa11079e444a\", > \"execute-for-coordinator\" => true, > \"domain-controller-lock-id\" => -1163262107 > } > } at resource [ > (\"profile\" => \"full\"), > (\"subsystem\" => \"elytron\"), > (\"jdbc-realm\" => \"xxxx\") > ] to subsystem 'elytron' model version '2.0.0' -- attributes [principal-query] WFLYCTL0302: The following attributes are not understood in the target model version and this resource will need to be ignored on the target host: [principal-query] > {code} > The error message should contain something like {{[principal-query[0].scram-mapper.hash-encoding]}} instead of {{[principal-query]}}. > The error message is misleading, as the attribute {{[principal-query]}} HAS TO be defined - only the {{hash-encoding}} must not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-215) Version all Jenkins Job Configs In Git

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-215?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-215: ------------------------------- Summary: Version all Jenkins Job Configs In Git (was: Move all Jenkins Job Configs to Git) > Version all Jenkins Job Configs In Git > -------------------------------------- > > Key: SWSQE-215 > URL: https://issues.jboss.org/browse/SWSQE-215 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 May 2018