December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4837) Abstract reflective accesses from RuleUnitDescription

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4837?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4837: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18) > Abstract reflective accesses from RuleUnitDescription > ----------------------------------------------------- > > Key: DROOLS-4837 > URL: https://issues.redhat.com/browse/DROOLS-4837 > Project: Drools > Issue Type: Feature Request > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > RuleUnitDescription interface returns `Method`s; in Kogito we need a way to abstract over class definitions so that a RuleUnit can be materialized at later stages of the compilation process. > with this JIRA, we introduce an abstraction over RuleUnitDescription, so that different implementations can be provided. The default implementation is reflective (uses Methods), but a non-reflective implementation will be allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4842) Parametrize Lambda Externalization

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4842: ------------------------------------ Summary: Parametrize Lambda Externalization Key: DROOLS-4842 URL: https://issues.redhat.com/browse/DROOLS-4842 Project: Drools Issue Type: Feature Request Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4841) Externalise Rule Unit's Lambdas

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4841: ------------------------------------ Summary: Externalise Rule Unit's Lambdas Key: DROOLS-4841 URL: https://issues.redhat.com/browse/DROOLS-4841 Project: Drools Issue Type: Feature Request Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1830) Verification & Validation: Management for the issue reporting

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1830?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1830. ------------------------------- Resolution: Won't Fix Closing this issue as was not reported by customer and no one had a look over two years. > Verification & Validation: Management for the issue reporting > ------------------------------------------------------------- > > Key: DROOLS-1830 > URL: https://issues.redhat.com/browse/DROOLS-1830 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > #1 issue: Reports keep popping up after each edit. > #2 issue: Depending what the dtable goals are, some issues are known and should happen. Reporting these over and over again is just useless noise. > Ideas for keeping the noise down: Make it possible to minimize the verification result panel to the side and only open when needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1869) [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1869?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1869. ------------------------------- Resolution: Won't Fix Closing this issue as was not reported by customer and no one had a look over two years. > [Guided Decision Table] ValidationWebWorkerServlet fails to load web worker > --------------------------------------------------------------------------- > > Key: DROOLS-1869 > URL: https://issues.redhat.com/browse/DROOLS-1869 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta4 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: beta5_smoketesting, dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > > The guided decision tables are not validated. After user clicks on the _Validate_ button, the error [1] appears in the server log. > Steps to reproduce: > # Create new Guided Decision Table > # Add simple Condition column into the table > # Insert new empty row into the table > # Click Validate button > ** Panel with validation results won't appear > ** The error in server log appear > [1] > {code:log} > 10:32:00,313 ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-43) Failed to load verifier web worker. > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1875) Guided Decision Table Verification: Make a selenium test for each issue type

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1875?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1875. ------------------------------- Resolution: Won't Fix Closing this issue as was not reported by customer and no one had a look over two years. > Guided Decision Table Verification: Make a selenium test for each issue type > ---------------------------------------------------------------------------- > > Key: DROOLS-1875 > URL: https://issues.redhat.com/browse/DROOLS-1875 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: verifier > > Best way would probably be upload different gdst files, then check the verification report result for each in the client. > Once the setup is done for one file it should be easy to reuse the setup for new files. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1871) [Guided Decision Table] Date field in simple condition and BRL fragment causes the verification to freeze

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1871?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1871. ------------------------------- Resolution: Won't Fix Closing this issue as was not reported by customer and no one had a look over two years. > [Guided Decision Table] Date field in simple condition and BRL fragment causes the verification to freeze > --------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1871 > URL: https://issues.redhat.com/browse/DROOLS-1871 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta4 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe, verifier > Attachments: Screenshot from 2016-12-14 10-54-03.png > > > If in the decision table simple condition based on Date field and any BRL fragment are used together, then the verification freezes as shown in the attachment. > Steps to reproduce: > # Open example mortgages project > # Navigate into org.mortgages package > # Create new Guided Decision Table > # Add simple condition column that check for applicationDate of an Applicant > # Add 5 rows into table and fill them with some values as shown in the attachment > # Add BRL condition column that checks if there exists Applicant of some age > # The verification will freeze as shown in the attachment -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1874) Verification reporting: Impossible match is detected just for equality operator

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1874?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1874. ------------------------------- Resolution: Done Closing this issue as was not reported by customer and no one had a look over two years. > Verification reporting: Impossible match is detected just for equality operator > ------------------------------------------------------------------------------- > > Key: DROOLS-1874 > URL: https://issues.redhat.com/browse/DROOLS-1874 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.CR2 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe, verifier > > The feature of detecting impossible match stopped to work for condition columns that uses operators less than and greater than. If the condition columns uses equality operator, then the impossible match is detected. > Steps to reproduce: > # Create Guided Decision Table > # Create two columns that do check like: *p : Person(name == [value])* > # Append row into table > # In first column check that name equals to "John" > # In second column check that name equals to "john" > # Impossible match is detected in this case > # Create another Guided Decision table > # Create one column that do check like: *p : Person(age < [value])* > # Create other column that do check like: *p : Person(age > [value])* > # Append row into the table > # Check that age is less than 10 in first column > # Check that age is greater than 20 in second column > # Impossible match *is not* thrown, but it is expected -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1874) Verification reporting: Impossible match is detected just for equality operator

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1874?page=com.atlassian.jira.plug... ] Jozef Marko reopened DROOLS-1874: --------------------------------- > Verification reporting: Impossible match is detected just for equality operator > ------------------------------------------------------------------------------- > > Key: DROOLS-1874 > URL: https://issues.redhat.com/browse/DROOLS-1874 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.CR2 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe, verifier > > The feature of detecting impossible match stopped to work for condition columns that uses operators less than and greater than. If the condition columns uses equality operator, then the impossible match is detected. > Steps to reproduce: > # Create Guided Decision Table > # Create two columns that do check like: *p : Person(name == [value])* > # Append row into table > # In first column check that name equals to "John" > # In second column check that name equals to "john" > # Impossible match is detected in this case > # Create another Guided Decision table > # Create one column that do check like: *p : Person(age < [value])* > # Create other column that do check like: *p : Person(age > [value])* > # Append row into the table > # Check that age is less than 10 in first column > # Check that age is greater than 20 in second column > # Impossible match *is not* thrown, but it is expected -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1874) Verification reporting: Impossible match is detected just for equality operator

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1874?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-1874. ------------------------------- Resolution: Won't Fix Closing this issue as was not reported by customer and no one had a look over two years. > Verification reporting: Impossible match is detected just for equality operator > ------------------------------------------------------------------------------- > > Key: DROOLS-1874 > URL: https://issues.redhat.com/browse/DROOLS-1874 > Project: Drools > Issue Type: Sub-task > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.CR2 > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Minor > Labels: reported-by-qe, verifier > > The feature of detecting impossible match stopped to work for condition columns that uses operators less than and greater than. If the condition columns uses equality operator, then the impossible match is detected. > Steps to reproduce: > # Create Guided Decision Table > # Create two columns that do check like: *p : Person(name == [value])* > # Append row into table > # In first column check that name equals to "John" > # In second column check that name equals to "john" > # Impossible match is detected in this case > # Create another Guided Decision table > # Create one column that do check like: *p : Person(age < [value])* > # Create other column that do check like: *p : Person(age > [value])* > # Append row into the table > # Check that age is less than 10 in first column > # Check that age is greater than 20 in second column > # Impossible match *is not* thrown, but it is expected -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019