[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ]
Jozef Marko closed DROOLS-5075.
-------------------------------
Resolution: Duplicate Issue
> [DMN Designer] properties panel is not refreshed for top level output header
> ----------------------------------------------------------------------------
>
> Key: DROOLS-5075
> URL: https://issues.redhat.com/browse/DROOLS-5075
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.34.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Minor
> Labels: drools-tools
>
> The issue was found during RHDM-1181 review, however it is probably not related.
> The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5075) [DMN Designer] properties panel is not refreshed for top level output header
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5075?page=com.atlassian.jira.plug... ]
Jozef Marko commented on DROOLS-5075:
-------------------------------------
Will be resolved as part of DROOLS-5060
> [DMN Designer] properties panel is not refreshed for top level output header
> ----------------------------------------------------------------------------
>
> Key: DROOLS-5075
> URL: https://issues.redhat.com/browse/DROOLS-5075
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.34.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Minor
> Labels: drools-tools
>
> The issue was found during RHDM-1181 review, however it is probably not related.
> The DMN Decision table expression can have complex output - structure/context. In such case output header cells are in two levels. The issue is if the top level output header cell is selected, the properties panel is not refreshed. It is an issue if previously was selected for example input header cell, then after selection change, an inappropriate information is shown in the properties panel.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-10388) Persistent EJB timer timed_object_id naming discrepancy
by Lukas Vydra (Jira)
[ https://issues.redhat.com/browse/WFLY-10388?page=com.atlassian.jira.plugi... ]
Lukas Vydra commented on WFLY-10388:
------------------------------------
Hi, I'm not able to reproduce this behaviour, are you still able to reproduce it? If so, could you please provide us with more detailed reprosteps, configuration, etc. ? Thank you
> Persistent EJB timer timed_object_id naming discrepancy
> -------------------------------------------------------
>
> Key: WFLY-10388
> URL: https://issues.redhat.com/browse/WFLY-10388
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Boris Pran
> Assignee: Lukas Vydra
> Priority: Major
>
> Persistent EJB timers created declaratively (with @Schedule) create timed_object_id without version information while timers created using TimerService API include version info from deployment unit.
> This way after version upgrade @Schedule timers survive but TimerService API created ones are lost and need to be created again.
> I also seems that old timers remain created or at least their definitions can be seen in jboss_ejb_timer table.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5076) Rule compilation fails with date constraints on nested fact types
by Matteo Casalino (Jira)
Matteo Casalino created DROOLS-5076:
---------------------------------------
Summary: Rule compilation fails with date constraints on nested fact types
Key: DROOLS-5076
URL: https://issues.redhat.com/browse/DROOLS-5076
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.33.0.Final, 7.32.0.Final
Reporter: Matteo Casalino
Assignee: Mario Fusco
Attachments: nested-date-constraint.tgz
As of Drools 7.32.0.Final, patterns containing constraints on nested dates won't compile.
For instance, given the following drl:
{noformat}
declare Fact
n : Nested
end
declare Nested
d : java.util.Date
end
rule "with nested date"
when
Fact(n!.d >= "01-Jan-2020", n!.d <= "10-Jan-2020")
then
end
{noformat}
we get the following error:
Message [id=1, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0
text=Unable to Analyse Expression n.d >= "01-Jan-2020":
[Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String]
[Near : {... n.d >= "01-Jan-2020" ....}]
^]
Message [id=2, kieBase=forall-date-constraint, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0
text=Unable to Analyse Expression n.d <= "10-Jan-2020":
[Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String]
[Near : {... n.d <= "10-Jan-2020" ....}]
^]
{noformat}
We don't reproduce with Drools <= 7.31.0.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months