September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2964) Shadow Network

by Mark Proctor (JIRA)

Mark Proctor created DROOLS-2964: ------------------------------------ Summary: Shadow Network Key: DROOLS-2964 URL: https://issues.jboss.org/browse/DROOLS-2964 Project: Drools Issue Type: Feature Request Reporter: Mark Proctor Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2962) Incremental and Non-Incremental evaluation instead of sequential mode.

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2962?page=com.atlassian.jira.plugi... ] Mark Proctor updated DROOLS-2962: --------------------------------- Labels: MDP_BRAINFARTS (was: ) > Incremental and Non-Incremental evaluation instead of sequential mode. > ---------------------------------------------------------------------- > > Key: DROOLS-2962 > URL: https://issues.jboss.org/browse/DROOLS-2962 > Project: Drools > Issue Type: Feature Request > Reporter: Mark Proctor > Assignee: Mario Fusco > Labels: MDP_BRAINFARTS > > While Drools supports sequential mode at the engine configuration level. We should move this to a unit and rule level. > We should enhance this work too. Right now Drools evaluation is either fully incremental or non-incremental if the kbase is set to stateless. > Sequential mode current means two things. > 1) Rules evaluate and fire in load order. > 2) Rules are non-incremental. > By default now all rules are load order anyway. If we simply supported a @NonIncremental or @Incremental(NO) attribute on a unit, then it's behaviour would be the same as sequential is now, but scoped to the unit. I believe this is true, but I'd like this verified (challenged). > As with existence/data driven, this is the default for the unit's rules. A unit may override with the opposite configuration. > This means a unit can be mixed incremental and non-incremental. > Existence or Data Driven annotations for non-incremental do not make sense, and their combination should throw an error, as explained below. > Instead a non-incremental rule should have control on whether it is to be re-evaluated and fired, each time the unit is entered. At first glance this behaviour looks very similar to Existence Driven, however the choice not to allow @ExistenceDriven + @NonIncremetal is due to the lack of symmetry. You could not combined @DataDriven + @NonIncremental. That lack of symmetry may break intuitive learning, if it's not kept clean. > If an alternative annotation is introduced - such as @OneShot|@EvalAndFireOnce|etc. We should make sure it fits intuitively and cleanly with how we explain @ExistenceDriven. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2961) Existence and Data Driven rule firing

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2961?page=com.atlassian.jira.plugi... ] Mark Proctor updated DROOLS-2961: --------------------------------- Labels: MDP_BRAINFARTS (was: ) > Existence and Data Driven rule firing > ------------------------------------- > > Key: DROOLS-2961 > URL: https://issues.jboss.org/browse/DROOLS-2961 > Project: Drools > Issue Type: Feature Request > Reporter: Mark Proctor > Assignee: Mario Fusco > Labels: MDP_BRAINFARTS > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4086) Starting an embedded server with older versions of WildFly Core results in a NoSuchMethodException

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4086?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4086: ------------------------------------- Component/s: CLI [~jfdenise] FYI. I believe this would affect the CLI embed-[server|host-controller] if the --jboss-home param was used and it pointed to a previous release. It would be nice to be able to test that but it's a pretty big pain. For the mixed-domain tests in full there's already some hooks for using legacy release zips if they are already present on the FS. And then for CI we ensure that they are present. Maybe something like that could be done for CLI testing. > Starting an embedded server with older versions of WildFly Core results in a NoSuchMethodException > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-4086 > URL: https://issues.jboss.org/browse/WFCORE-4086 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Embedded > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-3943 introduced a new method which accepts a class loader for the reflective invocation. This fails with any release of WildFly Core prior to 6.0.0.Alpha5 as the method including the class loader is not present. The method using the class loader should be checked and fallback to the method without the class loader parameter. > Note that this _may_ affect the migration tool which could require a 6.0.2.Final release of WildFly Core. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-433) Score Cards: PMML4Compiler fails to load PMML- KBases

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-433?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-433: ------------------------------------ poker: 8 > Score Cards: PMML4Compiler fails to load PMML- KBases > ----------------------------------------------------- > > Key: DROOLS-433 > URL: https://issues.jboss.org/browse/DROOLS-433 > Project: Drools > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Michael Anstis > Assignee: Lance Leverich > Labels: drools-core > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2397) PMML modules have classloader issues in OSGi

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2397?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2397: ------------------------------------- poker: 8 > PMML modules have classloader issues in OSGi > -------------------------------------------- > > Key: DROOLS-2397 > URL: https://issues.jboss.org/browse/DROOLS-2397 > Project: Drools > Issue Type: Bug > Affects Versions: 7.6.0.Final > Environment: Equinox OSGi container, Java 8 > Reporter: Jens Reimann > Assignee: Lance Leverich > Labels: drools-core > > The drools PMML modules (drools-pmml and kie-pmml) both suffer from a few class loader issues when running inside an OSGi container. > The KieBase built for transforming the PMML model to Drools model selects the wrong class loader (based on the context class loader). The JAXB instance creator fails with the same problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2961) Existence and Data Driven rule firing

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2961?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2961: ------------------------------------- poker: 13 > Existence and Data Driven rule firing > ------------------------------------- > > Key: DROOLS-2961 > URL: https://issues.jboss.org/browse/DROOLS-2961 > Project: Drools > Issue Type: Feature Request > Reporter: Mark Proctor > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2762: -------------------------------- Description: The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition): - This component must be disabled (or hidden) when an existing/primitive data type is selected. h3. Acceptance test - User not able to add and save lines that are filled just partially - Check added rows after reopening - Check undo redo commands - The "Add row" button must always appear to the user (e.q. a lot of item definitions present) was: The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition): - This component must be disabled (or hidden) when an existing/primitive data type is selected. h3. Acceptance test - User not able to add and save lines that are filled just partially - Check added rows after reopening - Check undo redo commands - The "Add row" button must always appear to the user > [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table) > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2762 > URL: https://issues.jboss.org/browse/DROOLS-2762 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > Attachments: DROOLS-2762.png > > > The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition): > - This component must be disabled (or hidden) when an existing/primitive data type is selected. > h3. Acceptance test > - User not able to add and save lines that are filled just partially > - Check added rows after reopening > - Check undo redo commands > - The "Add row" button must always appear to the user (e.q. a lot of item definitions present) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10976) Artemis warnings during startup

by Rich DiCroce (JIRA)

Rich DiCroce created WFLY-10976: ----------------------------------- Summary: Artemis warnings during startup Key: WFLY-10976 URL: https://issues.jboss.org/browse/WFLY-10976 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 14.0.0.Final Reporter: Rich DiCroce Assignee: Jeff Mesnil Artemis logs these warnings during startup when using the stock standalone-full.xml configuration: {code} 12:11:31,997 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ222269: Please use a fixed value for "journal-pool-files". Default changed per https://issues.apache.org/jira/browse/ARTEMIS-1628 12:11:32,000 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 62) AMQ221075: Usage of wildcardRoutingEnabled configuration property is deprecated, please use wildCardConfiguration.enabled instead {code} It looks like there's a config option that could be used to silence the first one, but I have no idea what the second one is talking about. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2961) Existence and Data Driven rule firing

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2961?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-2961: ---------------------------------------- poker: n/a > Existence and Data Driven rule firing > ------------------------------------- > > Key: DROOLS-2961 > URL: https://issues.jboss.org/browse/DROOLS-2961 > Project: Drools > Issue Type: Feature Request > Reporter: Mark Proctor > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018