[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3317?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3317:
--------------------------------
Labels: drools-tools (was: )
> Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-3317
> URL: https://issues.jboss.org/browse/DROOLS-3317
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.15.0.Final
> Reporter: Toni Rikkola
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Insert a fact with a boolean field in dtable RHS.
> The DRL generated looks like this:
> {code:java}
> rule "Row 3 The Table"
> dialect "mvel"
> when
> s : Source( age >= 18 , kitten == "Dog" )
> then
> s.setRisk( "ok" );
> DroolsUtil fact0 = new DroolsUtil();
> fact0.setARuleFired( true );
> insert( fact0 );
> end
> {code}
> The line
> {code:java}
> fact0.setARuleFired( true );
> {code}
> does not compile. It should be ( for example ):
> {code:java}
> fact0.aRuleFired = true;
> {code}
> The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3317?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3317:
--------------------------------
Affects Version/s: 7.15.0.Final
> Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-3317
> URL: https://issues.jboss.org/browse/DROOLS-3317
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.15.0.Final
> Reporter: Toni Rikkola
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Insert a fact with a boolean field in dtable RHS.
> The DRL generated looks like this:
> {code:java}
> rule "Row 3 The Table"
> dialect "mvel"
> when
> s : Source( age >= 18 , kitten == "Dog" )
> then
> s.setRisk( "ok" );
> DroolsUtil fact0 = new DroolsUtil();
> fact0.setARuleFired( true );
> insert( fact0 );
> end
> {code}
> The line
> {code:java}
> fact0.setARuleFired( true );
> {code}
> does not compile. It should be ( for example ):
> {code:java}
> fact0.aRuleFired = true;
> {code}
> The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-3317?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-3317:
---------------------------------
Workaround Description: The workaround is to use freeform DRL. (was: I guess the workaround is to use eval.)
> Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-3317
> URL: https://issues.jboss.org/browse/DROOLS-3317
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Michael Anstis
> Priority: Major
>
> Insert a fact with a boolean field in dtable RHS.
> The DRL generated looks like this:
> {code:java}
> rule "Row 3 The Table"
> dialect "mvel"
> when
> s : Source( age >= 18 , kitten == "Dog" )
> then
> s.setRisk( "ok" );
> DroolsUtil fact0 = new DroolsUtil();
> fact0.setARuleFired( true );
> insert( fact0 );
> end
> {code}
> The line
> {code:java}
> fact0.setARuleFired( true );
> {code}
> does not compile. It should be ( for example ):
> {code:java}
> fact0.aRuleFired = true;
> {code}
> The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
by Toni Rikkola (Jira)
Toni Rikkola created DROOLS-3317:
------------------------------------
Summary: Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
Key: DROOLS-3317
URL: https://issues.jboss.org/browse/DROOLS-3317
Project: Drools
Issue Type: Bug
Components: Guided Decision Table Editor
Reporter: Toni Rikkola
Assignee: Michael Anstis
Insert a fact with a boolean field in dtable RHS.
The DRL generated looks like this:
{code:java}
rule "Row 3 The Table"
dialect "mvel"
when
s : Source( age >= 18 , kitten == "Dog" )
then
s.setRisk( "ok" );
DroolsUtil fact0 = new DroolsUtil();
fact0.setARuleFired( true );
insert( fact0 );
end
{code}
The line
{code:java}
fact0.setARuleFired( true );
{code}
does not compile. It should be ( for example ):
{code:java}
fact0.aRuleFired = true;
{code}
The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3317) Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-3317?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-3317:
---------------------------------
Workaround Description: I guess the workaround is to use eval.
> Guided Decision Tables: Insert in RHS not creating valid code for boolean fields.
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-3317
> URL: https://issues.jboss.org/browse/DROOLS-3317
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Michael Anstis
> Priority: Major
>
> Insert a fact with a boolean field in dtable RHS.
> The DRL generated looks like this:
> {code:java}
> rule "Row 3 The Table"
> dialect "mvel"
> when
> s : Source( age >= 18 , kitten == "Dog" )
> then
> s.setRisk( "ok" );
> DroolsUtil fact0 = new DroolsUtil();
> fact0.setARuleFired( true );
> insert( fact0 );
> end
> {code}
> The line
> {code:java}
> fact0.setARuleFired( true );
> {code}
> does not compile. It should be ( for example ):
> {code:java}
> fact0.aRuleFired = true;
> {code}
> The above is done by inserting the fact with BRL action, but the same error bothers the "Set the value of field" option.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-9588) Investigate on splitting as transaction module to not be gathering all dependencies
by Yeray Borges (Jira)
[ https://issues.jboss.org/browse/WFLY-9588?page=com.atlassian.jira.plugin.... ]
Yeray Borges commented on WFLY-9588:
------------------------------------
[~ochaloup] Since it is related to this issue, I would like to add here the possibilty to remove two additional dependencies from org.jboss.as.xts module discussed by email. I point them out here so you can considerate if we should/should not remove them:
* org.jboss.ws.common
* org.jboss.threads
> Investigate on splitting as transaction module to not be gathering all dependencies
> -----------------------------------------------------------------------------------
>
> Key: WFLY-9588
> URL: https://issues.jboss.org/browse/WFLY-9588
> Project: WildFly
> Issue Type: Task
> Components: Transactions
> Affects Versions: 11.0.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Major
> Attachments: eap71-txn-dependencies.jpg
>
>
> Current org.jboss.as.transaction module is heavy lifting and has many dependencies and lot of work competencies. E.g. org.jboss.jts module depends on that too.
> It should be investigated how to disentangle all the dependencies.
> Plus this could be beneficiary for WildFly Swarm if we are able to split the dependency chains, maybe not using one big jar in the transaction module but provide more granularity. Needs to be investigated.
> See attached image for a view of dependencies.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months