[JBoss JIRA] (WFLY-13089) Upgrade MicroProfile REST Client implementation to 1.4
by Alessio Soldano (Jira)
Alessio Soldano created WFLY-13089:
--------------------------------------
Summary: Upgrade MicroProfile REST Client implementation to 1.4
Key: WFLY-13089
URL: https://issues.redhat.com/browse/WFLY-13089
Project: WildFly
Issue Type: Feature Request
Components: MP REST Client
Reporter: Alessio Soldano
Assignee: Ronald Sigal
We need to provide an implementation of the latest (1.4) MicroProfile REST Client spec. This is basically implying upgrading RESTEasy.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5064) DMN based Test Scenario has incorrect hint about number format
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5064:
-----------------------------------
Summary: DMN based Test Scenario has incorrect hint about number format
Key: DROOLS-5064
URL: https://issues.redhat.com/browse/DROOLS-5064
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Affects Versions: 7.34.0.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
DMN based Test Scenario cheatsheet contains incorrect entry:
_numbers and strings (strings must be delimited by quotation marks), for example "John Doe" or ""_
Numbers don't need to be wrapped by quotes.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5060) [DMN Designer] Editor allows node with prefix/trailing space
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5060?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5060:
-----------------------------------
Story Points: 5
Sprint: 2020 Week 07-09 (from Feb 10)
> [DMN Designer] Editor allows node with prefix/trailing space
> ------------------------------------------------------------
>
> Key: DROOLS-5060
> URL: https://issues.redhat.com/browse/DROOLS-5060
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Matteo Mortari
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: ItemDefinition-white-space.png
>
>
> I understand [DROOLS-5017] has been re-purposed to allow Info and Warn level messages be displayed on Stunner Validation dialog. That is fine.
> But, imho, an UX point is not being considered, where is necessary instead.
> By the DMN spec, a node should not have a prefix/trailing space, as space insensitivity would mandate 1 trailing or 2 trailing spaces are simply ignored etc.
> The engine is lenient to avoid this crashing the evaluation, but still is a bad designed model to persist the node name (DRGElement name and its corresponding variable name) with those extra spaces IMHO.
> Further, I consider is just the Analyst which slipped a space.
> In my perspective, the editor should just strip away the prefix/trailing space:
> * -While Importing a DMN model from file Upload- (See [DROOLS-5062|https://issues.redhat.com/browse/DROOLS-5062])
> * While editing a DRGElement and hitting OK to save its name
> For your consideration, thanks.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5050) Issue with alpha node and expired events rule execution
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5050?page=com.atlassian.jira.plug... ]
Luca Molteni updated DROOLS-5050:
---------------------------------
Sprint: 2020 Week 07-09 (from Feb 10)
> Issue with alpha node and expired events rule execution
> -------------------------------------------------------
>
> Key: DROOLS-5050
> URL: https://issues.redhat.com/browse/DROOLS-5050
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.33.0.Final
> Reporter: Marcell Pessanha Cruz
> Assignee: Luca Molteni
> Priority: Critical
>
> Alpha node based rules evaluated for expired events are not all executed during the inference cycle.
> With the following rules:
> {noformat}
> declare DummyEvent
> @role( event )
> @timestamp( eventTimestamp )
> @expires( 1s )
> end
> rule R1
> when
> $evt : DummyEvent()
> then
> end
> rule R2
> when
> $evt : ApplicationEvent()
> then
> end
> {noformat}
> and this code to execute:
> {noformat}
> public interface ApplicationEvent { }
> public static class DummyEvent implements ApplicationEvent {...}
> /* .... */
> final KieSession kieSession = kieBase.newKieSession( sessionConfig, null );
> PseudoClockScheduler clock = kieSession.getSessionClock();
> final long currentTime = clock.getCurrentTime();
> clock.advanceTime(10, TimeUnit.SECONDS);
> kieSession.insert(new DummyEvent(10, currentTime));
> kieSession.fireAllRules()
> {noformat}
> then only the *R1* rule is executed, not R2.
> Note: the same test case passes on 7.2.0.Final and earlier versions.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months