[JBoss JIRA] (WFCORE-5151) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5151?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-5151:
-------------------------------------
Affects Version/s: 13.0.0.Beta6
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFCORE-5151
> URL: https://issues.redhat.com/browse/WFCORE-5151
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 13.0.0.Beta6
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFCORE-5151) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-5151?page=com.atlassian.jira.plug... ]
Darran Lofthouse moved WFLY-13935 to WFCORE-5151:
-------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-5151 (was: WFLY-13935)
Component/s: Security
(was: Security)
Affects Version/s: (was: 15.0.0.Final)
(was: 16.0.0.Final)
(was: 17.0.0.Final)
(was: 18.0.0.Final)
(was: 19.0.0.Final)
(was: 20.0.0.Final)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFCORE-5151
> URL: https://issues.redhat.com/browse/WFCORE-5151
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Darran Lofthouse reassigned WFLY-13935:
---------------------------------------
Assignee: (was: Darran Lofthouse)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise reassigned WFLY-13935:
-------------------------------------------
Assignee: Darran Lofthouse (was: Jean Francois Denise)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Darran Lofthouse
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise updated WFLY-13935:
----------------------------------------
Component/s: Security
(was: CLI)
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13935:
---------------------------------------------
This issue is unrelated to CLI, the elytron subsystem handles attributes values.
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jan Stourac (Jira)
[ https://issues.redhat.com/browse/WFLY-13935?page=com.atlassian.jira.plugi... ]
Jan Stourac updated WFLY-13935:
-------------------------------
Attachment: reproducer.sh
> dir-contexts referral-mode attribute upper/lower case discrepancy
> -----------------------------------------------------------------
>
> Key: WFLY-13935
> URL: https://issues.redhat.com/browse/WFLY-13935
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Final, 19.0.0.Final, 20.0.0.Final
> Reporter: Jan Stourac
> Assignee: Jean Francois Denise
> Priority: Minor
> Attachments: reproducer.sh
>
>
> There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
> When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
> This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
> In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
> What is the issue here:
> # If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
> # If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (WFLY-13935) dir-contexts referral-mode attribute upper/lower case discrepancy
by Jan Stourac (Jira)
Jan Stourac created WFLY-13935:
----------------------------------
Summary: dir-contexts referral-mode attribute upper/lower case discrepancy
Key: WFLY-13935
URL: https://issues.redhat.com/browse/WFLY-13935
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 20.0.0.Final, 19.0.0.Final, 18.0.0.Final, 17.0.0.Final, 16.0.0.Final, 15.0.0.Final
Reporter: Jan Stourac
Assignee: Jean Francois Denise
Attachments: reproducer.sh
There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.
When there is no value set (default is applied), then particular value is printed in upper-case - {{IGNORE}}. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. {{ignore}} (lower-case is also saved in raw xml configuration).
This behavior started with {{WildFly 15.0.0.Final}} and is still present in {{WildFly 20.0.0.Final}}. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.
In {{WildFly 14.0.0.Final}} there was always upper-case value printed.
What is the issue here:
# If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
# If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5695) Lack of runtime type validation when running the simulation for a badly written DMN decision table
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5695?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5695:
--------------------------------
Description: I mistakenly populated a DMN decision table as in the screenshot attached. However when I try to evaluate the table with scenario simulaton I expected some sort of type analysis that could at least report an error since I populated with strings a column that was been labeled with type number. (was: I mistakenly populated a DMN decision table as in the screenshot attached. However when I saved it I expected some sort of static type analysis and validation that could at least report an error since I populated with strings a column that was been labeled with type number.)
> Lack of runtime type validation when running the simulation for a badly written DMN decision table
> --------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5695
> URL: https://issues.redhat.com/browse/DROOLS-5695
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Mario Fusco
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: screenshot-1.png
>
>
> I mistakenly populated a DMN decision table as in the screenshot attached. However when I try to evaluate the table with scenario simulaton I expected some sort of type analysis that could at least report an error since I populated with strings a column that was been labeled with type number.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (DROOLS-5695) Lack of runtime type validation when running the simulation for a badly written DMN decision table
by Mario Fusco (Jira)
Mario Fusco created DROOLS-5695:
-----------------------------------
Summary: Lack of runtime type validation when running the simulation for a badly written DMN decision table
Key: DROOLS-5695
URL: https://issues.redhat.com/browse/DROOLS-5695
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Mario Fusco
Assignee: Matteo Mortari
Attachments: screenshot-1.png
I mistakenly populated a DMN decision table as in the screenshot attached. However when I saved it I expected some sort of static type analysis and validation that could at least report an error since I populated with strings a column that was been labeled with type number.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months