[Red Hat JIRA] (WFLY-13978) YAML support for system properties
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13978?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13978:
---------------------------------------------
Another possible use-case detailed in there: https://github.com/wildfly-extras/wildfly-jar-maven-plugin/issues/181#iss...
> YAML support for system properties
> -----------------------------------
>
> Key: WFLY-13978
> URL: https://issues.redhat.com/browse/WFLY-13978
> Project: WildFly
> Issue Type: Feature Request
> Components: Management
> Reporter: Marc Gabriel-Willem
> Assignee: Brian Stansberry
> Priority: Major
> Labels: WildFly
>
> Hi,
> In order to facilitate the migration from Thorntail to WildFly bootable JAR based solution I could be very nice to support YAML configuration file for system properties.
> Currently using the --properties WF parameter properties file only can be provided.
> The smallrye-config-source-yaml project does not help for system properties.
> It means all existing YAML files need to be converted to properties format and it hurts the Thorntail->WildFly migration.
> I hope this feature could be analysed..and integrated ;)
> BR,
> Marc
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 months
[Red Hat JIRA] (DROOLS-5938) In accumulate implemention of executable model field binding overtake pattern binding even when not appropiate
by Mario Fusco (Jira)
Mario Fusco created DROOLS-5938:
-----------------------------------
Summary: In accumulate implemention of executable model field binding overtake pattern binding even when not appropiate
Key: DROOLS-5938
URL: https://issues.redhat.com/browse/DROOLS-5938
Project: Drools
Issue Type: Bug
Components: executable model
Reporter: Mario Fusco
Assignee: Mario Fusco
When translated into the executable model the following rule works correctly
{code:java}
global java.util.List result;
rule R when
$acc1 : Collection() from accumulate(
$p : Person( ), collectSet( $p ) )
then
result.add($acc1.iterator().next());
end{code}
but if a field binding is added to the accumulated pattern like in
{code:java}
global java.util.List result;
rule R when
$acc1 : Collection() from accumulate(
$p : Person( $name : name ), collectSet( $p ) )
then
result.add($acc1.iterator().next());
end {code}
then the accumulation is wrongly performed on the bound field, the person's name in this case, instead of on the Person object itself as specified in the accumulating function.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 months
[Red Hat JIRA] (DROOLS-5897) Compound BigDecimal operator is translated to assignOperator in MVEL
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5897?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi reassigned DROOLS-5897:
-----------------------------------------
Assignee: Toshiya Kobayashi (was: Luca Molteni)
> Compound BigDecimal operator is translated to assignOperator in MVEL
> --------------------------------------------------------------------
>
> Key: DROOLS-5897
> URL: https://issues.redhat.com/browse/DROOLS-5897
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Luca Molteni
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> {code:java}
> @Test
> @Ignore("without B it doesn't work on MVEL")
> public void testCompoundOperator() throws Exception {
> // DROOLS-5894
> String drl =
> "import " + Person.class.getCanonicalName() + "\n" +
> "dialect \"mvel\"\n" +
> "rule R\n" +
> "when\n" +
> " $p : Person( age >= 26 )\n" +
> "then\n" +
> " $p.money += 50000;\n" +
> "end";
> KieSession ksession = getKieSession(drl);
> Person john = new Person("John", 30);
> john.setMoney( new BigDecimal( 70000 ) );
> ksession.insert(john);
> assertEquals(1, ksession.fireAllRules());
> assertEquals(new BigDecimal( 120000 ), john.getMoney());
> }{code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 months
[Red Hat JIRA] (DROOLS-5937) Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL.
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5937?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5937:
--------------------------------------
Story Points: 4
> Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5937
> URL: https://issues.redhat.com/browse/DROOLS-5937
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
> Labels: support
> Attachments: reproducer_02801729_6_mvel.zip, reproducer_02801729_6e_6f.zip
>
>
> Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL (org.mvel2).
> When using MVEL.eval method, the result of "+=" operation is incorrect, and "-=", "*=", "/=" operations result in an error.
> - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B)
> -- $bus.weight += 1000 ==> 1000 // incorrect result
> -- $bus.weight -= 1000 ==> Error
> -- $bus.weight *= 1000 ==> Error
> -- $bus.weight /= 1000 ==> Error
> - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively)
> -- $bus.weight += bdv ==> 1000 // incorrect result
> -- $bus.weight -= bdv ==> Error
> -- $bus.weight *= bdv ==> Error
> -- $bus.weight /= bdv ==> Error
> When using MVEL.executeExpression method, the result of "+=" operation is correct, while "-=", "*=", "/=" operations cause an error.
> - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B)
> -- $bus.weight += 1000 ==> 13000 // correct
> -- $bus.weight -= 1000 ==> Error
> -- $bus.weight *= 1000 ==> Error
> -- $bus.weight /= 1000 ==> Error
> - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively)
> -- $bus.weight += bdv ==> 13000 // correct
> -- $bus.weight -= bdv ==> Error
> -- $bus.weight *= bdv ==> Error
> -- $bus.weight /= bdv ==> Error
> $bus.weight is a BigDecimal type property.
> MVEL library should return correct result for any operations above.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 months
[Red Hat JIRA] (DROOLS-5937) Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL.
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5937?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi moved RHDM-1558 to DROOLS-5937:
-------------------------------------------------
Component/s: core engine
(was: BRE)
Docs QE Status: NEW
Key: DROOLS-5937 (was: RHDM-1558)
QE Status: NEW
Affects Version/s: 7.48.0.Final
(was: 7.9.0.GA)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Environment: (was: The issue was found in RHDM 7.9.0.)
Project: Drools (was: Red Hat Decision Manager)
> Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5937
> URL: https://issues.redhat.com/browse/DROOLS-5937
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.48.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
> Labels: support
> Attachments: reproducer_02801729_6_mvel.zip, reproducer_02801729_6e_6f.zip
>
>
> Compound assignment operation like BigDecimal_type_property <op> Numeric/BigDecimal_value causes an unexpected result or error in MVEL (org.mvel2).
> When using MVEL.eval method, the result of "+=" operation is incorrect, and "-=", "*=", "/=" operations result in an error.
> - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B)
> -- $bus.weight += 1000 ==> 1000 // incorrect result
> -- $bus.weight -= 1000 ==> Error
> -- $bus.weight *= 1000 ==> Error
> -- $bus.weight /= 1000 ==> Error
> - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively)
> -- $bus.weight += bdv ==> 1000 // incorrect result
> -- $bus.weight -= bdv ==> Error
> -- $bus.weight *= bdv ==> Error
> -- $bus.weight /= bdv ==> Error
> When using MVEL.executeExpression method, the result of "+=" operation is correct, while "-=", "*=", "/=" operations cause an error.
> - BigDecimal_type_property <op> Numeric_value (Initial value of $bus.weight is 12000B)
> -- $bus.weight += 1000 ==> 13000 // correct
> -- $bus.weight -= 1000 ==> Error
> -- $bus.weight *= 1000 ==> Error
> -- $bus.weight /= 1000 ==> Error
> - BigDecimal_type_property <op> BigDecimal_value (Initial value of $bus.weight and bdv are 12000B and 1000B respectively)
> -- $bus.weight += bdv ==> 13000 // correct
> -- $bus.weight -= bdv ==> Error
> -- $bus.weight *= bdv ==> Error
> -- $bus.weight /= bdv ==> Error
> $bus.weight is a BigDecimal type property.
> MVEL library should return correct result for any operations above.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 9 months