February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5986) DMN Alpha Network - Multiple Decision Tables in DMN File

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5986?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5986: --------------------------------- Description: It's possible to have multiple decision table in a DMN file, that means that we should generate different AlphaNetwork creation classes and avoid collision on Feel tests (was: When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which the first results of the output is returned. Support different Hit Policies) > DMN Alpha Network - Multiple Decision Tables in DMN File > -------------------------------------------------------- > > Key: DROOLS-5986 > URL: https://issues.redhat.com/browse/DROOLS-5986 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > It's possible to have multiple decision table in a DMN file, that means that we should generate different AlphaNetwork creation classes and avoid collision on Feel tests -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5986) DMN Alpha Network - Multiple Decision Tables in DMN File

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5986: ------------------------------------ Summary: DMN Alpha Network - Multiple Decision Tables in DMN File Key: DROOLS-5986 URL: https://issues.redhat.com/browse/DROOLS-5986 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Luca Molteni Assignee: Luca Molteni When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which the first results of the output is returned. Support different Hit Policies -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5985) DMN Alpha Network - Support different Hit Policies

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5985?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5985: --------------------------------- Description: When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which the first results of the output is returned. Support different Hit Policies was: Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). > DMN Alpha Network - Support different Hit Policies > -------------------------------------------------- > > Key: DROOLS-5985 > URL: https://issues.redhat.com/browse/DROOLS-5985 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > When using Alpha Network for DMN there's only a single hardcoded Hit Policy in which the first results of the output is returned. > Support different Hit Policies -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5984: --------------------------------- Description: Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). We will be able to enhance it in another JIRA? (was: Verify that indexes are generated correctly. This should also give some performance different, try measure it with a benchmark.) > DMN Alpha Network - Range Indexing > ---------------------------------- > > Key: DROOLS-5984 > URL: https://issues.redhat.com/browse/DROOLS-5984 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). We will be able to enhance it in another JIRA? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5985) DMN Alpha Network - Support different Hit Policies

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5985: ------------------------------------ Summary: DMN Alpha Network - Support different Hit Policies Key: DROOLS-5985 URL: https://issues.redhat.com/browse/DROOLS-5985 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Luca Molteni Assignee: Luca Molteni Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5984: --------------------------------- Description: Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). was:Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. Also we would need to change range index threshold to test easier). We will be able to enhance it in another JIRA? > DMN Alpha Network - Range Indexing > ---------------------------------- > > Key: DROOLS-5984 > URL: https://issues.redhat.com/browse/DROOLS-5984 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Currently alpha range index is not enabled probably because AlphaNetworkCreation.createAlphaNode() doesn't set an index to a constraint for "Application Risk Score" in DMNDecisionTableAlphaSupportingTest (= ConstraintType is UNKNOWN so CompositeObjectSinkAdapter.isRangeIndexable() returns false. > Also we would need to change range index threshold to test easier). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5984) DMN Alpha Network - Range Indexing

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5984: ------------------------------------ Summary: DMN Alpha Network - Range Indexing Key: DROOLS-5984 URL: https://issues.redhat.com/browse/DROOLS-5984 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Luca Molteni Assignee: Luca Molteni Verify that indexes are generated correctly. This should also give some performance different, try measure it with a benchmark. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5983) DMN Alpha Network - Verify Indexing

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5983?page=com.atlassian.jira.plug... ] Luca Molteni reassigned DROOLS-5983: ------------------------------------ Assignee: Luca Molteni (was: Matteo Mortari) > DMN Alpha Network - Verify Indexing > ----------------------------------- > > Key: DROOLS-5983 > URL: https://issues.redhat.com/browse/DROOLS-5983 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Verify that indexes are generated correctly. > This should also give some performance different, try measure it with a benchmark. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5983) DMN Alpha Network - Verify Indexing

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5983: ------------------------------------ Summary: DMN Alpha Network - Verify Indexing Key: DROOLS-5983 URL: https://issues.redhat.com/browse/DROOLS-5983 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Luca Molteni Assignee: Matteo Mortari Verify that indexes are generated correctly. This should also give some performance different, try measure it with a benchmark. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14338) JSF: ajax listener not invoked

by Jens a (Jira)

[ https://issues.redhat.com/browse/WFLY-14338?page=com.atlassian.jira.plugi... ] Jens a commented on WFLY-14338: ------------------------------- My attached reproducer didn't contain a h:form. Adding the form resolves the issue in the reproducer. However I still experience the issue in a project where the image tags are within an outputPanel which is within a form. I will try to create this as a reproducer > JSF: ajax listener not invoked > ------------------------------ > > Key: WFLY-14338 > URL: https://issues.redhat.com/browse/WFLY-14338 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 21.0.2.Final > Reporter: Jens a > Assignee: Farah Juma > Priority: Major > Attachments: primefaces-test-master.zip > > > Primefaces ajax component doesn't call listener, however the onsuccess and oncomplete JS is executed. > This issue has been reviewed by the Primefaces team: it is not reproducable on Jetty, so they claim it to be a WildFly specific issue (see full discussion at [https://stackoverflow.com/questions/65810607)] > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

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 February 2021