November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2121) Add support for weekday "field" for dates

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2121: ------------------------------------- Summary: Add support for weekday "field" for dates Key: DROOLS-2121 URL: https://issues.jboss.org/browse/DROOLS-2121 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.4.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.5.0.Final FEEL doesn't currently have a way to calculate the weekday a date falls on. Suggestion is to use a field notation for it. E.g.: someDate.weekday date("2017-11-08").weekday -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2120) in FEEL, date +/- duration is returning null

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2120: ------------------------------------- Summary: in FEEL, date +/- duration is returning null Key: DROOLS-2120 URL: https://issues.jboss.org/browse/DROOLS-2120 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.4.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.5.0.Final In FEEL, a "date" can replace a "date and time" value anywhere it is required, by implicitly converting it with time set to "00:00:00". Currently, addition and subtraction between date and duration is not working as it should, based on table 45 of the DMN spec. E.g: date + duration date - duration -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2119) append() function does not support non-list first argument

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2119: ------------------------------------- Summary: append() function does not support non-list first argument Key: DROOLS-2119 URL: https://issues.jboss.org/browse/DROOLS-2119 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.4.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.5.0.Final The spec defines an axiom of [a]=a , i.e., singleton lists are equal to the single element and vice-versa. The current implementation for the append() function requires a list as the first element, but should accept a single element as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2118) DMN extension REST /dmn to list inputData and itemDefs

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2118: -------------------------------------- Summary: DMN extension REST /dmn to list inputData and itemDefs Key: DROOLS-2118 URL: https://issues.jboss.org/browse/DROOLS-2118 Project: Drools Issue Type: Enhancement Components: dmn engine, kie server Reporter: Matteo Mortari Assignee: Edson Tirelli Currently /dmn enlist the model coordinates and the list of DMN Decisions. In order to be more complete from a client perspective, it is also required for it to enlist: * the list of DMN InputData, so to know which inputs are required for the model evaluation * the ItemDefinitions so to know of which types are the inputs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Matthew Stevens updated DROOLS-1825: ------------------------------------ Attachment: DecisionTable1.png DecisionTable2.png > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX > Attachments: DROOLS-1825 (Parent Rule).png, DecisionTable1.png, DecisionTable2.png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-1825: ----------------------------------------- As you know, the process designer and data object assets have a property panel. We could try that if it isn't too much work. I will attach a very rough mockup. > [Guided Decision Table] Ability to change HIT policy in a decision table anytime > -------------------------------------------------------------------------------- > > Key: DROOLS-1825 > URL: https://issues.jboss.org/browse/DROOLS-1825 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Ivo Bek > Assignee: Toni Rikkola > Priority: Critical > Labels: UX > Attachments: DROOLS-1825 (Parent Rule).png > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy. > Thus, it should be possible to change HIT policy in a decision table anytime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9537) EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-9537?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink edited comment on WFLY-9537 at 11/8/17 12:03 PM: ------------------------------------------------------------------ I wrote a tests for this but did not issued a PR for now. https://github.com/wfink/wildfly/tree/WFLY-9537 -> https://github.com/wfink/wildfly/commit/11cb7b731f492f61bb89a468650a90be0... The test include two timezone's "Berlin/Europe" and "America/Los_Angeles". The Berlin test CEST>CET fail on my machine; which runs in the default "Berlin" TZ. The related LA test is not failing even if the JVM default timezone for the test is set to -> -Duser.timezone="America/Los_Angeles" At this point it is unclear to my why this is not failing for both. The Java doc for GregorianCalendar [1] shows that setting a time will prefer the default TZ with standard time. This means to me: - set a time between Nov.29. 2:00...3:00 will use the CET time as CET and CEST are valid so the standard winter time is used - any time outside will use CEST (before 2:00) and CET (after 3:00) [1] http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-... was (Author: wdfink): I wrote a tests for this but did not issued a PR for now. https://github.com/wfink/wildfly/tree/WFLY-9537 -> https://github.com/wfink/wildfly/commit/11cb7b731f492f61bb89a468650a90be0... The test include two timezone's "Berlin/Europe" and "America/Los_Angeles". The Berlin test CEST>CET fail on my machine; which runs in the default "Berlin" TZ. The related LA test is not failing even if the JVM default timezone for the test is set to -> -Duser.timezone="America/Los_Angeles" At this point it is unclear to my why this is not failing for both. The Java doc for GregorianCalendar [1] shows that setting a time will prefer the default TZ with standard time. This means to me: - set a time between Nov.29. 2:00...3:00 will use the CET time as CET and CEST are valid so the standard winter time is used > EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9537 > URL: https://issues.jboss.org/browse/WFLY-9537 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Environment: Here CEST -> CET change from 2017 Nov. 29 2:00 CEST .... 2017 Nov. 29 2:00 CET > Reporter: Wolf-Dieter Fink > Assignee: Eduardo Martins > > If a calendar timer has a schedule less than an hour, and should fire during the DST switch it is expected to be fired like this: > Asume : @Schedule(hour="*", minute="5/15", timezone="Europe/Berlin") > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CEST > 2017 Nov. 29 2:20 CEST > 2017 Nov. 29 2:35 CEST > 2017 Nov. 29 2:50 CEST > 2017 Nov. 29 2:05 CET > But the timer is fired like this: > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CET > All events within that hour are lost! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9537) EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-9537?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-9537: ---------------------------------------- I wrote a tests for this but did not issued a PR for now. https://github.com/wfink/wildfly/tree/WFLY-9537 -> https://github.com/wfink/wildfly/commit/11cb7b731f492f61bb89a468650a90be0... The test include two timezone's "Berlin/Europe" and "America/Los_Angeles". The Berlin test CEST>CET fail on my machine; which runs in the default "Berlin" TZ. The related LA test is not failing even if the JVM default timezone for the test is set to -> -Duser.timezone="America/Los_Angeles" At this point it is unclear to my why this is not failing for both. The Java doc for GregorianCalendar [1] shows that setting a time will prefer the default TZ with standard time. This means to me: - set a time between Nov.29. 2:00...3:00 will use the CET time as CET and CEST are valid so the standard winter time is used > EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9537 > URL: https://issues.jboss.org/browse/WFLY-9537 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Environment: Here CEST -> CET change from 2017 Nov. 29 2:00 CEST .... 2017 Nov. 29 2:00 CET > Reporter: Wolf-Dieter Fink > Assignee: Eduardo Martins > > If a calendar timer has a schedule less than an hour, and should fire during the DST switch it is expected to be fired like this: > Asume : @Schedule(hour="*", minute="5/15", timezone="Europe/Berlin") > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CEST > 2017 Nov. 29 2:20 CEST > 2017 Nov. 29 2:35 CEST > 2017 Nov. 29 2:50 CEST > 2017 Nov. 29 2:05 CET > But the timer is fired like this: > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CET > All events within that hour are lost! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9537) EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-9537?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink reassigned WFLY-9537: -------------------------------------- Assignee: Eduardo Martins > EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9537 > URL: https://issues.jboss.org/browse/WFLY-9537 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Environment: Here CEST -> CET change from 2017 Nov. 29 2:00 CEST .... 2017 Nov. 29 2:00 CET > Reporter: Wolf-Dieter Fink > Assignee: Eduardo Martins > > If a calendar timer has a schedule less than an hour, and should fire during the DST switch it is expected to be fired like this: > Asume : @Schedule(hour="*", minute="5/15", timezone="Europe/Berlin") > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CEST > 2017 Nov. 29 2:20 CEST > 2017 Nov. 29 2:35 CEST > 2017 Nov. 29 2:50 CEST > 2017 Nov. 29 2:05 CET > But the timer is fired like this: > 2017 Nov. 29 1:50 CEST > 2017 Nov. 29 2:05 CET > All events within that hour are lost! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9537) EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-9537: -------------------------------------- Summary: EJB Timer is not fired during the ambiguous hour during the switch from summer to winter times Key: WFLY-9537 URL: https://issues.jboss.org/browse/WFLY-9537 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 11.0.0.Final Environment: Here CEST -> CET change from 2017 Nov. 29 2:00 CEST .... 2017 Nov. 29 2:00 CET Reporter: Wolf-Dieter Fink If a calendar timer has a schedule less than an hour, and should fire during the DST switch it is expected to be fired like this: Asume : @Schedule(hour="*", minute="5/15", timezone="Europe/Berlin") 2017 Nov. 29 1:50 CEST 2017 Nov. 29 2:05 CEST 2017 Nov. 29 2:20 CEST 2017 Nov. 29 2:35 CEST 2017 Nov. 29 2:50 CEST 2017 Nov. 29 2:05 CET But the timer is fired like this: 2017 Nov. 29 1:50 CEST 2017 Nov. 29 2:05 CET All events within that hour are lost! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2017