[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4461:
-----------------------------------
Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4))
> Use date picker for LocalDate
> -----------------------------
>
> Key: DROOLS-4461
> URL: https://issues.redhat.com/browse/DROOLS-4461
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor
> Reporter: Toni Rikkola
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> We should use the date picker for LocalDate like we do for Date.
> h2. Acceptance test
> - Define *Applicant(born after [lit_value])* constraint
> - Define *Applicant(born after [temp_key])* constraint
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-2845:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4))
> Extend the existing verifier to support DMN tables
> --------------------------------------------------
>
> Key: DROOLS-2845
> URL: https://issues.redhat.com/browse/DROOLS-2845
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Optional
> Labels: UX, drools-tools, verifier
>
> h1. Goal
> Merge the Validation methods DMN has with the generic Validator that is used by the GDST.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5331) Support for Enums in Rule Test Scenario
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5331?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5331:
-----------------------------------
Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25) (was: 2020 Week 19-21 (from May 4))
> Support for Enums in Rule Test Scenario
> ---------------------------------------
>
> Key: DROOLS-5331
> URL: https://issues.redhat.com/browse/DROOLS-5331
> Project: Drools
> Issue Type: Feature Request
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> Currently, Test Scenario doesn't support an attribute of Enumeration type.
> In case of RULE Scenario:
> Loading a Data Object with such attribute, will result in Complex Type properties with a nested simple property "declaringClass" of "java.lang.Class" type.
> The expected result should be a Simple property of Enum type (in this case: category [java.lang.Enum] )
> In case of DMN Scenario:
> Currently no impacts
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5370) DMN DT Analysis 1NF duplicate error and avoid subsumption dups
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-5370:
--------------------------------------
Summary: DMN DT Analysis 1NF duplicate error and avoid subsumption dups
Key: DROOLS-5370
URL: https://issues.redhat.com/browse/DROOLS-5370
Project: Drools
Issue Type: Enhancement
Components: dmn engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
Following [DROOLS-3970] and [DROOLS-3779] when a 1NF violation is detected for a duplicate rule, level is Error. Further, Subsumption message pertaining to the same duplicate rules is redundant, so it should be silenced to the end-user.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5290) Executable model compiled throws exception in accumulate pattern matching
by Luca Molteni (Jira)
[ https://issues.redhat.com/browse/DROOLS-5290?page=com.atlassian.jira.plug... ]
Luca Molteni resolved DROOLS-5290.
----------------------------------
Release Notes Text: https://github.com/lucamolteni/drools/commit/bb23413a4c544997a5cabe8e9e48...
Resolution: Done
> Executable model compiled throws exception in accumulate pattern matching
> -------------------------------------------------------------------------
>
> Key: DROOLS-5290
> URL: https://issues.redhat.com/browse/DROOLS-5290
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Reporter: Luca Molteni
> Assignee: Luca Molteni
> Priority: Major
>
> Customer is encountering below issue while rule execution if they use executable model.
> {code:java}
> Exception in thread "main" java.lang.RuntimeException: java.lang.ClassCastException: org.drools.core.reteoo.SubnetworkTuple
> cannot be cast to java.lang.Long
> at org.drools.core.rule.SingleAccumulate.accumulate(SingleAccumulate.java:105)
> at org.drools.core.phreak.PhreakAccumulateNode.addMatch(PhreakAccumulateNode.java:714)
> at org.drools.core.phreak.PhreakAccumulateNode.doLeftInserts(PhreakAccumulateNode.java:168)
> at org.drools.core.phreak.PhreakAccumulateNode.doNode(PhreakAccumulateNode.java:89)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:581)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:552)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:379)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:339)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalStackEntry(RuleNetworkEvaluator.java:237)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:180)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5369) [DMN Designer] Boxed expressions - Decision Table - Output clause - Selecting a structured type, sub-columns are auto-created
by Valentino Pellegrino (Jira)
Valentino Pellegrino created DROOLS-5369:
--------------------------------------------
Summary: [DMN Designer] Boxed expressions - Decision Table - Output clause - Selecting a structured type, sub-columns are auto-created
Key: DROOLS-5369
URL: https://issues.redhat.com/browse/DROOLS-5369
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Affects Versions: 7.18.0.Final
Reporter: Valentino Pellegrino
Assignee: Valentino Pellegrino
Whenever user selects a structured type, the output clauses columns get created with all fields belonging to the chosen structured type
h2. We can't make the user lose data
if the user already has a column with any data typed in, we have to keep it.
h2. Acceptance criteria
- Action should be undoable/redoable, especially if user had structure data type, more columns with a lot of data and mistakenly change to simple type, i.e. single column
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-3685) [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type
by Valentino Pellegrino (Jira)
[ https://issues.redhat.com/browse/DROOLS-3685?page=com.atlassian.jira.plug... ]
Valentino Pellegrino updated DROOLS-3685:
-----------------------------------------
Description:
When creating a decision table, output clauses columns should be created based on the type of the output node.
This is what we are already doing for the input columns, that are created based on the type of the input node. The flow is described in the GIF below:
!image-2020-05-25-10-56-36-376.png|thumbnail!
was:
When users select a "Structured" Data Type in a Decision Table output clause, the Data Type fields should be automatically shown as "sub-cells".
h2. Acceptance criteria
- Action should be undoable/redoable, especially if user had structure data type, more columns with a lot of data and mistakenly change to simple type, i.e. single column
Attachment: image-2020-05-25-10-56-36-376.png
Summary: [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type (was: [DMN Designer] Boxed expressions - Decision Table - Output clause - Show Data Type fields automatically)
> [DMN Designer] Boxed expressions - Decision Table - Output clause - Creating Decision Table, sub-columns are auto-created for structured type
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3685
> URL: https://issues.redhat.com/browse/DROOLS-3685
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Guilherme Gomes
> Assignee: Valentino Pellegrino
> Priority: Major
> Labels: drools-tools
> Attachments: image-2020-05-25-10-56-36-376.png
>
>
> When creating a decision table, output clauses columns should be created based on the type of the output node.
> This is what we are already doing for the input columns, that are created based on the type of the input node. The flow is described in the GIF below:
> !image-2020-05-25-10-56-36-376.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13305) Bootable jar for Wildfly
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-13305?page=com.atlassian.jira.plugi... ]
Jean Francois Denise commented on WFLY-13305:
---------------------------------------------
[~jamezp], this was created as an upstream for the EAP issue. I don't expect changes in the Wildfly repo, just the proposal.
> Bootable jar for Wildfly
> ------------------------
>
> Key: WFLY-13305
> URL: https://issues.redhat.com/browse/WFLY-13305
> Project: WildFly
> Issue Type: Feature Request
> Components: Server
> Reporter: Jean Francois Denise
> Assignee: Jean Francois Denise
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Provides support for running MicroService apps without the need archive it as a deployment and without the need to deploy it in a running application server.
> Provides support for ability to run MicroService apps on the Operating Systems command line as a bootable jar.
> Provides support for developing and running the app. "java -jar app.jar" and maven command line interface.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month