[JBoss JIRA] (DROOLS-5119) [Guided Rule Editor] Workbench BigDecimal value turns into 0.0 in DRL
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5119?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5119:
-----------------------------------
Affects Version/s: (was: 7.34.0.Final)
> [Guided Rule Editor] Workbench BigDecimal value turns into 0.0 in DRL
> ---------------------------------------------------------------------
>
> Key: DROOLS-5119
> URL: https://issues.redhat.com/browse/DROOLS-5119
> Project: Drools
> Issue Type: Bug
> Components: Examples (Workbench), Guided Rule Editor
> Reporter: Bhala Hadkar
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-5119-rule.png, Workbench-Guided-Rule.png, drools.png
>
>
> When I set up a Guided rule on Workbench having a comparison condition on one of the domain field of type Big Decimal then the int value entered through literal text disappears and turns into 0.0B.
> For e.g. if you look at this Guided Rule screenshot the literal value 100 turned into 0.0.
> !Workbench-Guided-Rule.png|thumbnail!
> Also in the drools the value becomes 0.0B.
> !drools.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (LOGMGR-266) log4j2-jboss-logmanager LevelTranslator NullPointer
by James Perkins (Jira)
[ https://issues.redhat.com/browse/LOGMGR-266?page=com.atlassian.jira.plugi... ]
James Perkins updated LOGMGR-266:
---------------------------------
Description:
We found the following Nullpointer Exception
{code}
Caused by: java.lang.NullPointerException
at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95)
at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156)
{code}
....
Reason seems that LevelTranslator is not defensive enough. Suggestion:
{code}
java.util.logging.Level translateLevel(final Level level) {
//level null is same as level not translated
if(level == null) {
return org.jboss.logmanager.Level.INFO;
}
final java.util.logging.Level result = log4jToJul.get(level.intLevel());
return result == null ? org.jboss.logmanager.Level.INFO : result;
}
Level translateLevel(final java.util.logging.Level level) {
//level null is same as level not translated
if(level == null) {
return Level.INFO;
}
final Level result = julToLog4j.get(level.intValue());
return result == null ? Level.INFO : result;
}
{code}
was:
We found the following Nullpointer Exception
Caused by: java.lang.NullPointerException
at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95)
at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156)
....
Reason seems that LevelTranslator is not defensive enough. Suggestion:
java.util.logging.Level translateLevel(final Level level) {
//level null is same as level not translated
if(level == null) {
return org.jboss.logmanager.Level.INFO;
}
final java.util.logging.Level result = log4jToJul.get(level.intLevel());
return result == null ? org.jboss.logmanager.Level.INFO : result;
}
Level translateLevel(final java.util.logging.Level level) {
//level null is same as level not translated
if(level == null) {
return Level.INFO;
}
final Level result = julToLog4j.get(level.intValue());
return result == null ? Level.INFO : result;
}
> log4j2-jboss-logmanager LevelTranslator NullPointer
> ---------------------------------------------------
>
> Key: LOGMGR-266
> URL: https://issues.redhat.com/browse/LOGMGR-266
> Project: JBoss Log Manager
> Issue Type: Bug
> Reporter: Boris Unckel
> Priority: Critical
>
> We found the following Nullpointer Exception
> {code}
> Caused by: java.lang.NullPointerException
> at org.jboss.logmanager.log4j.LevelTranslator.translateLevel(LevelTranslator.java:95)
> at org.jboss.logmanager.log4j.JBossLogger.getLevel(JBossLogger.java:156)
> {code}
> ....
> Reason seems that LevelTranslator is not defensive enough. Suggestion:
> {code}
> java.util.logging.Level translateLevel(final Level level) {
> //level null is same as level not translated
> if(level == null) {
> return org.jboss.logmanager.Level.INFO;
> }
> final java.util.logging.Level result = log4jToJul.get(level.intLevel());
> return result == null ? org.jboss.logmanager.Level.INFO : result;
> }
> Level translateLevel(final java.util.logging.Level level) {
> //level null is same as level not translated
> if(level == null) {
> return Level.INFO;
> }
> final Level result = julToLog4j.get(level.intValue());
> return result == null ? Level.INFO : result;
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5119) [Guided Rule Editor] Workbench BigDecimal value turns into 0.0 in DRL
by Bhala Hadkar (Jira)
[ https://issues.redhat.com/browse/DROOLS-5119?page=com.atlassian.jira.plug... ]
Bhala Hadkar commented on DROOLS-5119:
--------------------------------------
This works perfectly fine with version 7.34.0.Final. This issue can be closed. Thanks [~manstis].
> [Guided Rule Editor] Workbench BigDecimal value turns into 0.0 in DRL
> ---------------------------------------------------------------------
>
> Key: DROOLS-5119
> URL: https://issues.redhat.com/browse/DROOLS-5119
> Project: Drools
> Issue Type: Bug
> Components: Examples (Workbench), Guided Rule Editor
> Affects Versions: 7.34.0.Final
> Reporter: Bhala Hadkar
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: DROOLS-5119-rule.png, Workbench-Guided-Rule.png, drools.png
>
>
> When I set up a Guided rule on Workbench having a comparison condition on one of the domain field of type Big Decimal then the int value entered through literal text disappears and turns into 0.0B.
> For e.g. if you look at this Guided Rule screenshot the literal value 100 turned into 0.0.
> !Workbench-Guided-Rule.png|thumbnail!
> Also in the drools the value becomes 0.0B.
> !drools.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5138) Collection editor for List of Objects
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5138?page=com.atlassian.jira.plug... ]
Jozef Marko commented on DROOLS-5138:
-------------------------------------
What do you mean by enum type please? like java wile with enum inside or business central enum asset?
> Collection editor for List of Objects
> -------------------------------------
>
> Key: DROOLS-5138
> URL: https://issues.redhat.com/browse/DROOLS-5138
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.35.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2020-03-09 16-06-05.png, bpms_dates.zip
>
>
> There is issue in Test Scenarios when user invokes the collection editor for {{java.util.List<java.lang.Object>}} field.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5167) Collection editor for Nested Generic List
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5167?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5167:
---------------------------------
Description:
Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
{code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
Expected: the cell is available to input expression.
Actual: cannot edit the cell.
See [^nestedGeneric.webm]
was:
Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
{code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
Expected: the cell is avalible to input expression
Actual:
> Collection editor for Nested Generic List
> ------------------------------------------
>
> Key: DROOLS-5167
> URL: https://issues.redhat.com/browse/DROOLS-5167
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.35.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: MySpace_Traffic4222312160964203593.zip, nestedGeneric.webm
>
>
> Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
> {code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
> Expected: the cell is available to input expression.
> Actual: cannot edit the cell.
> See [^nestedGeneric.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5167) Collection editor for Nested Generic List
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5167?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5167:
---------------------------------
Description:
Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
{code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
Expected: the cell is avalible to input expression
Actual:
was:There is issue in Test Scenarios when user invokes the collection editor for {{java.util.List<java.lang.Object>}} field.
> Collection editor for Nested Generic List
> ------------------------------------------
>
> Key: DROOLS-5167
> URL: https://issues.redhat.com/browse/DROOLS-5167
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.35.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: MySpace_Traffic4222312160964203593.zip, nestedGeneric.webm
>
>
> Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
> {code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
> Expected: the cell is avalible to input expression
> Actual:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5167) Collection editor for Nested Generic List
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5167?page=com.atlassian.jira.plug... ]
Anna Dupliak updated DROOLS-5167:
---------------------------------
Attachment: nestedGeneric.webm
> Collection editor for Nested Generic List
> ------------------------------------------
>
> Key: DROOLS-5167
> URL: https://issues.redhat.com/browse/DROOLS-5167
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.35.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: MySpace_Traffic4222312160964203593.zip, nestedGeneric.webm
>
>
> Unexpected behavior occures in Test Scenarios when user invokes the collection editor for Nested generic
> {code} # list= new java.util.List<java.util.List<String>>(); o = new java.util.List<String>;o.add("word");list.add(o);list;{code}
> Expected: the cell is avalible to input expression
> Actual:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months