[JBoss JIRA] (DROOLS-3921) QCon Presentation
by Edoardo Vacchi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3921?page=com.atlassian.jira.plugi... ]
Edoardo Vacchi resolved DROOLS-3921.
------------------------------------
Resolution: Done
> QCon Presentation
> -----------------
>
> Key: DROOLS-3921
> URL: https://issues.jboss.org/browse/DROOLS-3921
> Project: Drools
> Issue Type: Task
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
>
> Complete slides and possibly source code example (both *deliverables*) for the presentation:
> bq. *Your Program as a Transpiler: Applying Compiler Design to Everyday Programming*
> bq. Many languages “transpile” into other languages, but compilers are still often seen as arcane pieces of software that only a master of the dark arts could write. But at the end of the day, both are programs that translate code from a programming language to another.
> bq. So what does make a transpiler simple and a compiler hard? What can we learn from these complex pieces of software? And are they really that complex?
> bq. The lessons we can learn from language implementation design patterns are really within the reach of everyone; not only can they apply to daily programming problems, but they are also key to really understand the basis of exciting new technologies such as the GraalVM project and the Quarkus stack. In our experience on the Drools and jBPM projects, we have come across many opportunities to apply programming language development techniques to a broader context. In this talk, we will see some of these examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3973) Codegen'd rule unit should override reflective bind
by Edoardo Vacchi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3973?page=com.atlassian.jira.plugi... ]
Edoardo Vacchi updated DROOLS-3973:
-----------------------------------
Sprint: 2019 Week 17-19
> Codegen'd rule unit should override reflective bind
> ---------------------------------------------------
>
> Key: DROOLS-3973
> URL: https://issues.jboss.org/browse/DROOLS-3973
> Project: Drools
> Issue Type: Bug
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core, submarine
> Fix For: 8.0.0.Final
>
>
> native binary generation NPEs upon reflective operations on unit's POJO; but no reflective operations should occur, because code generation should override the body of the method doing reflection with a code generated version. However, this part was implemented in jBPM for processes, but not in rules.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3973) Codegen'd rule unit should override reflective bind
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3973:
--------------------------------------
Summary: Codegen'd rule unit should override reflective bind
Key: DROOLS-3973
URL: https://issues.jboss.org/browse/DROOLS-3973
Project: Drools
Issue Type: Bug
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
Fix For: 8.0.0.Final
native binary generation NPEs upon reflective operations on unit's POJO; but no reflective operations should occur, because code generation should override the body of the method doing reflection with a code generated version. However, this part was implemented in jBPM for processes, but not in rules.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Almas Toimbekov (Jira)
[ https://issues.jboss.org/browse/DROOLS-3972?page=com.atlassian.jira.plugi... ]
Almas Toimbekov updated DROOLS-3972:
------------------------------------
Steps to Reproduce:
{code:java}
rule "Rule 1"
salience 30
when
then
Resource resource1 = new Resource();
resource1.setName("Resource 1");
resource1.setAmount("5");
insert(resource1);
System.out.println("First");
end
rule "Rule 2"
salience 20
//no-loop - next rule fires if use 'update()' instead
when
$resource1: Resource(name == "Resource 1")
then
modify($resource1) {setAmount("20")};
// update($resource1);
System.out.println("Second");
end
rule "Rule 3"
salience 30
when
$resource1: Resource(name == "Resource 1", Double.parseDouble(amount) == "20")
// - interesting that the line below fires this rule
// $resource1: Resource(name == "Resource 1", amount.startsWith("20"))
then
System.out.println("Rule is fired"); //doesn't fire
end
{code}
was:
rule "Rule 1"
salience 30
when
then
Resource resource1 = new Resource();
resource1.setName("Resource 1");
resource1.setAmount("5");
insert(resource1);
System.out.println("First");
end
rule "Rule 2"
salience 20
//no-loop - next rule fires if use 'update()' instead
when
$resource1: Resource(name == "Resource 1")
then
modify($resource1) {setAmount("20")};
// update($resource1);
System.out.println("Second");
end
rule "Rule 3"
salience 30
when
$resource1: Resource(name == "Resource 1", Double.parseDouble(amount) == "20")
// - interesting that the line below fires this rule
// $resource1: Resource(name == "Resource 1", amount.startsWith("20"))
then
System.out.println("Rule is fired"); //doesn't fire
end
> Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3972
> URL: https://issues.jboss.org/browse/DROOLS-3972
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.20.0.Final
> Environment: Ubuntu
> Reporter: Almas Toimbekov
> Assignee: Luca Molteni
> Priority: Major
> Labels: double, evaluation, execution, parse
>
> When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3972) Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
by Almas Toimbekov (Jira)
Almas Toimbekov created DROOLS-3972:
---------------------------------------
Summary: Evaluation of facts hasn't been affected by 'modify()' when parsing String to Double
Key: DROOLS-3972
URL: https://issues.jboss.org/browse/DROOLS-3972
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.20.0.Final
Environment: Ubuntu
Reporter: Almas Toimbekov
Assignee: Luca Molteni
When I modify amount in an example below from 5 to 20 (both are Strings) and then try to evaluate this fact parsing it to Double - the third rule doesn't fire. But it fires when use 'update()' instead of 'modify() {}'
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3731:
-------------------------------------------
[~manstis] [~danielezonca] [~roger.martinez] Hi, just playing around with some ideas for this based on the precondition of navigating users from the Scenario Test tool to the DMN editor, if I'm understanding the suggestion ^^. I tried a version using a docked panel instead of a popover widget. My concern with the pop-over is principally about overloading with canvas nodes with too many interactive elements, so I want to explore alternatives.
!Test-error.png|thumbnail!
If there was a test report panel in DMN similar to Scenario we could use that for detailed node error info, along with providing test overview info, and actions like clearing the Error/s if that applies? I'm hoping this test dock could act like a Test "mode." So if you opened the property dock instead (or switched that toggle) it would show the regular model view. I don't know, I haven't thought it through fully, just brainstorming. :) Let me know, thanks!
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-3731:
--------------------------------------
Attachment: Test-error.png
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: Test-error.png, download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months