[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in constraint
by Luca Molteni (Jira)
[ https://issues.jboss.org/browse/DROOLS-3800?page=com.atlassian.jira.plugi... ]
Luca Molteni commented on DROOLS-3800:
--------------------------------------
[~mfusco] read above, I've created this https://issues.jboss.org/browse/DROOLS-3849
> Parser error with executable-model on Map literal expression in constraint
> --------------------------------------------------------------------------
>
> Key: DROOLS-3800
> URL: https://issues.jboss.org/browse/DROOLS-3800
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.18.0.Final
> Environment: 7.18.0.Final
> 7.18.0.Final-redhat-00002 (RHDM7.3.0)
> 7.14.0.Final-redhat-00004 (RHDM7.1.2)
> Reporter: Hiroko Miura
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: MapLiteralTest.zip
>
>
> When MAP literal expression is used in LHS like the following
> {noformat}
> when
> $fact: Fact(
> calc(["src":name, "target":"TEST"])
> )
> ...
> {noformat}
> KieBase build as Executable Model fails with parser error like:
> {noformat}
> org.drools.javaparser.ParseProblemException:
> Encountered unexpected token: "[" "["
> at line 1, column 6.
> Was expecting one of:
> ")"
> {noformat}
> This error does not happen when building this rule as normal kjar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3849) Different default with property reactivity with DRL and Exec Model
by Luca Molteni (Jira)
Luca Molteni created DROOLS-3849:
------------------------------------
Summary: Different default with property reactivity with DRL and Exec Model
Key: DROOLS-3849
URL: https://issues.jboss.org/browse/DROOLS-3849
Project: Drools
Issue Type: Enhancement
Components: executable model
Affects Versions: 7.20.0.Final
Reporter: Luca Molteni
Assignee: Mario Fusco
This test
Regression3800Test.testPropertyReactivityHanging
loop forever while using the executable model because of the default in property reactivity BitMask (0 vs MAX_LONG)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in constraint
by Luca Molteni (Jira)
[ https://issues.jboss.org/browse/DROOLS-3800?page=com.atlassian.jira.plugi... ]
Luca Molteni commented on DROOLS-3800:
--------------------------------------
This was fixed in https://github.com/kiegroup/drools/pull/2300/files
While doing it, we discovered a new bug with the attached reproducer.
So if you want to verify it, please add "result != "OK" to the condition as did here https://github.com/kiegroup/drools/pull/2300/files#diff-64fe2a87cd932377e... otherwise the rule with loop forever.
We're going to resolve the other bug in a separate JIRA
> Parser error with executable-model on Map literal expression in constraint
> --------------------------------------------------------------------------
>
> Key: DROOLS-3800
> URL: https://issues.jboss.org/browse/DROOLS-3800
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.18.0.Final
> Environment: 7.18.0.Final
> 7.18.0.Final-redhat-00002 (RHDM7.3.0)
> 7.14.0.Final-redhat-00004 (RHDM7.1.2)
> Reporter: Hiroko Miura
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: MapLiteralTest.zip
>
>
> When MAP literal expression is used in LHS like the following
> {noformat}
> when
> $fact: Fact(
> calc(["src":name, "target":"TEST"])
> )
> ...
> {noformat}
> KieBase build as Executable Model fails with parser error like:
> {noformat}
> org.drools.javaparser.ParseProblemException:
> Encountered unexpected token: "[" "["
> at line 1, column 6.
> Was expecting one of:
> ")"
> {noformat}
> This error does not happen when building this rule as normal kjar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-3702:
----------------------------------------
Not really able to tell about Stunner "strategies" but what I can tell is that from DMNDI perspective the location of the start of the connection and end of the connection is provided in terms of x,y. Anything which get us close to the DMNDI will be the better preference imho.
> [Stunner] Arrows are incorrectly positioned when save-open diagram
> ------------------------------------------------------------------
>
> Key: DROOLS-3702
> URL: https://issues.jboss.org/browse/DROOLS-3702
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
> Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif
>
>
> 1. Add a `Decision Node`
> 2. Add a `Input Data Node` bellow `Decision Node`
> 3. Connect `Input Data Node` to `Decision Node`
> 4. Save
> 5. Close
> 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned.
> I noticed this in DMN Showcase and in drools-wb.
> And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3702:
----------------------------------------
Hi [~roger600],
I agree that when nodes are added in the UI they appear to be using AUTO (is this new?!)
I also had a quick look at our marshaller and you are correct "...I understand that DMN marshallers are not supporting this _auto-magnet_ strategy...". It definitely appears to be setting magnets using {{MagnetConnection.Builder.at(..)}} which is {{FIXED}} where as I assume we should be using something more like {{MagnetConnection.Builder.atCenter(..)}} if we want them centred. I tried and tested this and is makes re-opening diagrams much nicer!
In reality however, if we want to preserve the original magnets set in the UI when adding Nodes, we need to preserve Stunner's magnet strategy. Failing to do so means we can only intelligently decide between {{CENTRE}} (the connection end-point is equal to the centre of the {{View}}) or {{AUTO}} (we would not be able to differentiate between {{AUTO}} and {{FIXED}} just by inspecting the geometry).
So, [~tirelli] and/or [~tari_manga] what do you prefer?
# Store additional extensions in the DMN file for Stunner's magnet strategy
# Default to either CENTRE or AUTO depending on a quick check to ascertain if the connection end-point is at the centre of the node.
We'd need to use the above default when opening diagrams not authored with our tooling as they'd lack the meta-data.
> [Stunner] Arrows are incorrectly positioned when save-open diagram
> ------------------------------------------------------------------
>
> Key: DROOLS-3702
> URL: https://issues.jboss.org/browse/DROOLS-3702
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Daniel José dos Santos
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
> Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif
>
>
> 1. Add a `Decision Node`
> 2. Add a `Input Data Node` bellow `Decision Node`
> 3. Connect `Input Data Node` to `Decision Node`
> 4. Save
> 5. Close
> 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned.
> I noticed this in DMN Showcase and in drools-wb.
> And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-3848) Internals may expect value is Comparable
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3848:
--------------------------------------
Summary: Internals may expect value is Comparable
Key: DROOLS-3848
URL: https://issues.jboss.org/browse/DROOLS-3848
Project: Drools
Issue Type: Bug
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
can compare days and time duration:
max(duration("PT6M"), duration("PT5M")) => PT6M
but can’t copmapre year and month duration:
max(duration("P6Y"), duration("P5Y")) => null
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month