[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal Expression cells clip multi-line expression
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3513?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3513:
-------------------------------------
[~manstis] Hi, adding comment here so I can upload and dmn asset, when I open attached dmn file in workbench, I see the attached error in server log.
> [DMN Designer] Literal Expression cells clip multi-line expression
> ------------------------------------------------------------------
>
> Key: DROOLS-3513
> URL: https://issues.jboss.org/browse/DROOLS-3513
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Thomas Mantegazzi
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: a12.dmn, error.log, image-2019-01-14-09-12-40-849.png
>
>
> If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box.
> !image-2019-01-14-09-12-40-849.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal Expression cells clip multi-line expression
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3513?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3513:
--------------------------------
Attachment: error.log
> [DMN Designer] Literal Expression cells clip multi-line expression
> ------------------------------------------------------------------
>
> Key: DROOLS-3513
> URL: https://issues.jboss.org/browse/DROOLS-3513
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Thomas Mantegazzi
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: a12.dmn, error.log, image-2019-01-14-09-12-40-849.png
>
>
> If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box.
> !image-2019-01-14-09-12-40-849.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal Expression cells clip multi-line expression
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3513?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3513:
--------------------------------
Attachment: a12.dmn
> [DMN Designer] Literal Expression cells clip multi-line expression
> ------------------------------------------------------------------
>
> Key: DROOLS-3513
> URL: https://issues.jboss.org/browse/DROOLS-3513
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Thomas Mantegazzi
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: a12.dmn, error.log, image-2019-01-14-09-12-40-849.png
>
>
> If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box.
> !image-2019-01-14-09-12-40-849.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-2850) Create a Verifier client side adapter for DMN tables
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-2850?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-2850:
---------------------------------
Sprint: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50, 2018 Week 51-01 (was: 2018 Week 39-41, 2018 Week 42-44, 2018 Week 45-47, 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01)
> Create a Verifier client side adapter for DMN tables
> ----------------------------------------------------
>
> Key: DROOLS-2850
> URL: https://issues.jboss.org/browse/DROOLS-2850
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, verifier
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1797) Incorrect V&V results when operator is filled in the row (as opposed to column definition)
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-1797?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-1797:
---------------------------------
Sprint: 2019 Week 02-04
> Incorrect V&V results when operator is filled in the row (as opposed to column definition)
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-1797
> URL: https://issues.jboss.org/browse/DROOLS-1797
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 6.4.0.Final
> Reporter: Anton Giertli
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, support, verifier
> Attachments: 6iOx.png
>
>
> Imagine data model Person with attribute age.
> If you create decision table and add two columns:
> - both are defined against "age" attribute
> - none of them have operator defined
> then you add one row, and you fill in the operator and the value directly inside the row.
> For example:
> >= 20
> <= 30
> The generated DRL looks like this:
> {code:java}
> package org;
> //from row number: 1
> rule "Row 1 AnotherTest"
> dialect "mvel"
> when
> p : Person( age >= 20 , age <= 30 )
> then
> p.setAgeGroup( "whatever" );
> end
> {code}
> The V&V will report this as conflicting row:
> !6iOx.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ]
Toni Rikkola closed DROOLS-3283.
--------------------------------
Resolution: Duplicate
> Incorrect V&V results when operator is filled in the row (as opposed to column definition)
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-3283
> URL: https://issues.jboss.org/browse/DROOLS-3283
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.14.0.Final
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: drools-tools, support, verifier
>
> Imagine data model Person with attribute age.
> If you create decision table and add two columns:
> - both are defined against "age" attribute
> - none of them have operator defined
> then you add one row, and you fill in the operator and the value directly inside the row.
> For example:
> >= 20
> <= 30
> The generated DRL looks like this:
> {code:java}
> package org;
> //from row number: 1
> rule "Row 1 AnotherTest"
> dialect "mvel"
> when
> p : Person( age >= 20 , age <= 30 )
> then
> p.setAgeGroup( "whatever" );
> end
> {code}
> The V&V will report this as conflicting row:
> !6iOx.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1797) Incorrect V&V results when operator is filled in the row (as opposed to column definition)
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-1797?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-1797:
---------------------------------
Labels: drools-tools support verifier (was: verifier)
> Incorrect V&V results when operator is filled in the row (as opposed to column definition)
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-1797
> URL: https://issues.jboss.org/browse/DROOLS-1797
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 6.4.0.Final
> Reporter: Anton Giertli
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools, support, verifier
> Attachments: 6iOx.png
>
>
> Imagine data model Person with attribute age.
> If you create decision table and add two columns:
> - both are defined against "age" attribute
> - none of them have operator defined
> then you add one row, and you fill in the operator and the value directly inside the row.
> For example:
> >= 20
> <= 30
> The generated DRL looks like this:
> {code:java}
> package org;
> //from row number: 1
> rule "Row 1 AnotherTest"
> dialect "mvel"
> when
> p : Person( age >= 20 , age <= 30 )
> then
> p.setAgeGroup( "whatever" );
> end
> {code}
> The V&V will report this as conflicting row:
> !6iOx.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11590) Cancelled timer not removed from internal cache when using persistent timers
by Jörg Bäsner (Jira)
[ https://issues.jboss.org/browse/WFLY-11590?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-11590:
-------------------------------
Steps to Reproduce:
1.) 2 WildFly server with the same configuration using an EJB timer with DB persistence.
2.) the attached application ({{playground-jar.jar}}) that starts 2 timer (1 _scanner_ timer and 1 _future_ timer)
- the _scanner_ timer runs every couple of seconds (e. g. 4 sec)
- the _future_ timer will never execute, it is always only _cancelled_ and newly _created_ by the _scanner_ timer (always adding 1 hour)
3.) running both servers with simple {{standalone.xml}} with persistent database timer with a _refresh-interval_ of 2000 (2 seconds) configuration and a port offset
It can be observed that the output for {{getTimers()}} on one node will increase in it's number.
was:
1.) 2 WildFly server with the same configuration using an EJB timer with DB persistence.
2.) the attached application that starts 2 timer (1 _scanner_ timer and 1 _future_ timer)
- the _scanner_ timer runs every couple of seconds (e. g. 4 sec)
- the _future_ timer will never execute, it is always only _cancelled_ and newly _created_ by the _scanner_ timer (always adding 1 hour)
3.) running both servers with simple {{standalone.xml}} with persistent database timer with a _refresh-interval_ of 2000 (2 seconds) configuration and a port offset
It can be observed that the output for {{getTimers()}} on one node will increase in it's number.
> Cancelled timer not removed from internal cache when using persistent timers
> ----------------------------------------------------------------------------
>
> Key: WFLY-11590
> URL: https://issues.jboss.org/browse/WFLY-11590
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 15.0.1.Final
> Environment: * 2 WildFly server running the same application (not necessarily clustered), but using the same database persistence for timers
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
> Priority: Major
> Attachments: playground-jar.jar, playground.zip
>
>
> When using database persistence for timers, the timers that are _synced_ via the {{RefreshTask}} and lateron _removed_ by the {{RefreshTask}} will not be deleted from the internal {{[timers|https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/timerservice/TimerServiceImpl.java#L120]}} _cache_ in {{[TimerServiceImpl.java|https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/timerservice/TimerServiceImpl.java#L1326]}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-1797) Incorrect V&V results when operator is filled in the row (as opposed to column definition)
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-1797?page=com.atlassian.jira.plugi... ]
Toni Rikkola reopened DROOLS-1797:
----------------------------------
> Incorrect V&V results when operator is filled in the row (as opposed to column definition)
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-1797
> URL: https://issues.jboss.org/browse/DROOLS-1797
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 6.4.0.Final
> Reporter: Anton Giertli
> Assignee: Toni Rikkola
> Priority: Major
> Labels: verifier
> Attachments: 6iOx.png
>
>
> Imagine data model Person with attribute age.
> If you create decision table and add two columns:
> - both are defined against "age" attribute
> - none of them have operator defined
> then you add one row, and you fill in the operator and the value directly inside the row.
> For example:
> >= 20
> <= 30
> The generated DRL looks like this:
> {code:java}
> package org;
> //from row number: 1
> rule "Row 1 AnotherTest"
> dialect "mvel"
> when
> p : Person( age >= 20 , age <= 30 )
> then
> p.setAgeGroup( "whatever" );
> end
> {code}
> The V&V will report this as conflicting row:
> !6iOx.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11590) Cancelled timer not removed from internal cache when using persistent timers
by Jörg Bäsner (Jira)
[ https://issues.jboss.org/browse/WFLY-11590?page=com.atlassian.jira.plugin... ]
Jörg Bäsner updated WFLY-11590:
-------------------------------
Attachment: playground-jar.jar
> Cancelled timer not removed from internal cache when using persistent timers
> ----------------------------------------------------------------------------
>
> Key: WFLY-11590
> URL: https://issues.jboss.org/browse/WFLY-11590
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 15.0.1.Final
> Environment: * 2 WildFly server running the same application (not necessarily clustered), but using the same database persistence for timers
> Reporter: Jörg Bäsner
> Assignee: Jörg Bäsner
> Priority: Major
> Attachments: playground-jar.jar, playground.zip
>
>
> When using database persistence for timers, the timers that are _synced_ via the {{RefreshTask}} and lateron _removed_ by the {{RefreshTask}} will not be deleted from the internal {{[timers|https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/timerservice/TimerServiceImpl.java#L120]}} _cache_ in {{[TimerServiceImpl.java|https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/timerservice/TimerServiceImpl.java#L1326]}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months