December 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-607) Match.getObjects() should reflect the patterns' order

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-607?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-607: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta5) > Match.getObjects() should reflect the patterns' order > ----------------------------------------------------- > > Key: DROOLS-607 > URL: https://issues.jboss.org/browse/DROOLS-607 > Project: Drools > Issue Type: Enhancement > Affects Versions: 5.5.0.Final, 5.6.0.Final, 6.0.0.Final, 6.1.0.Final > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 7.0.0.CR1 > > > if Match.getObjects() is called on a rule with LHS A() B() C(), > the resulting list will have the matching objects in reversed order > - that is, [c, b, a] - making it more difficult to analyze it. > The object's position in the list should reflect the LHS. > The order should be preserved even when subnetworks are present. > For example, A() not B() C() should then result in the list [a, *, c ] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-670) Generalize inline casts to work with traits

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-670?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-670: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta5) > Generalize inline casts to work with traits > ------------------------------------------- > > Key: DROOLS-670 > URL: https://issues.jboss.org/browse/DROOLS-670 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Davide Sottara > Fix For: 7.0.0.CR1 > > > The following constraint > {code} > Person( this#Worker( wage > 1000 ) ) > {code} > is admissible when Worker is a subtype of Person. > It should also be possible to use "#" when Worker is a donned trait. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-680) "contains" operator behaves inconsistently when used with Maps

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-680?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-680: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta5) > "contains" operator behaves inconsistently when used with Maps > -------------------------------------------------------------- > > Key: DROOLS-680 > URL: https://issues.jboss.org/browse/DROOLS-680 > Project: Drools > Issue Type: Bug > Affects Versions: 5.6.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.CR4 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > In a rule > {code} > Bean( map contains "x" ) // assuming "map" is a property of type Map > {code} > "contains" is arbitrarily interpreted as "containsKey" > The constrain will then fail after being jitted > The documentation explicitly states that "contains" applies to collections -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-817) Extremely poor performance of the topological sorting implementation for type declarations performs

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-817?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-817: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta5) > Extremely poor performance of the topological sorting implementation for type declarations performs > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-817 > URL: https://issues.jboss.org/browse/DROOLS-817 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 6.0.0.Final, 6.0.1.Final, 6.1.0.Final, 6.2.0.Final, 6.3.0.Beta1 > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 7.0.0.CR1 > > > The current implementation suffers from thrashing. > In case of large business object models (e.g. derived from an ontology), > the analysis at package build time may take orders of magnitude more > than necessary -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-744) Rule Generation Feature Request

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-744?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-744: ------------------------------------------ Fix Version/s: 7.0.0.CR1 (was: 7.0.0.Beta5) > Rule Generation Feature Request > ------------------------------- > > Key: DROOLS-744 > URL: https://issues.jboss.org/browse/DROOLS-744 > Project: Drools > Issue Type: Feature Request > Components: core engine, kie server > Affects Versions: 6.2.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Fix For: 7.0.0.CR1 > > > As a developer using Drools, I want a rule generation java api that supports control logic in the rule templates (e.g. for loops, if/else) and integrates with the rule workbench in order to build highly dynamic business rules driven systems. > The initial thought process around implementation is to build two things 1) a simple way to author mvel templates in business central, the existing text editor could be used at first and 2) a simple embedded java api in it's own maven module which can checkout the git project that has the mvel template, apply a set of domain objects to the template, check in the resulting rule files to the local git repo and then push the changes back to business central. This allows us to leverage the power of the existing MVEL and JGit tech stack while pushing the complexity to a java api, where we are stronger than the workbench itself. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7834) A test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412]

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFLY-7834?page=com.atlassian.jira.plugin.... ] Peter Palaga updated WFLY-7834: ------------------------------- Summary: A test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412] (was: Test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412]) > A test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412] > ------------------------------------------------------------------------------------------------ > > Key: WFLY-7834 > URL: https://issues.jboss.org/browse/WFLY-7834 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Peter Palaga > Assignee: Peter Palaga > > Add an integration test that will prove that SECURITY-930 and WFLY-7412 were properly fixed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-735) Remove unwanted OptaPlanner references from website sources

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-735?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer resolved DROOLS-735. ------------------------------------------- Resolution: Done > Remove unwanted OptaPlanner references from website sources > ----------------------------------------------------------- > > Key: DROOLS-735 > URL: https://issues.jboss.org/browse/DROOLS-735 > Project: Drools > Issue Type: Bug > Reporter: Petr Široký > Assignee: Michael Biarnes Kiefer > > There are still some unwanted references to OptaPlanner in the Drools website sources. For example the https://github.com/droolsjbpm/drools-website/blob/master/_config/site.yml contains keywords related to OptaPlanner rather than Drools. > There are probably others. We need to fix those. > Note: not every reference is necessarily unwanted. There may be some links or other info about OptaPlanner that we want to keep there. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7834) Test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412]

by Peter Palaga (JIRA)

Peter Palaga created WFLY-7834: ---------------------------------- Summary: Test for loading custom login modules from non-default JBoss modules [SECURITY-930][WFLY-7412] Key: WFLY-7834 URL: https://issues.jboss.org/browse/WFLY-7834 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Peter Palaga Assignee: Peter Palaga Add an integration test that will prove that SECURITY-930 and WFLY-7412 were properly fixed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2141) JMX notifications for ControlledProcessState changes are not updated when the running mode changes

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2141?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2141: -------------------------------------- Summary: JMX notifications for ControlledProcessState changes are not updated when the running mode changes (was: JMX notifications for ControlledProcessState changes are not sent in admin-only mode) > JMX notifications for ControlledProcessState changes are not updated when the running mode changes > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-2141 > URL: https://issues.jboss.org/browse/WFCORE-2141 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > JMX notifications added by https://issues.jboss.org/browse/EAP7-471 are not sent in admin-only mode. When notifications are active and the server gets reloaded into admin-only mode, only the normal->stopping transition is received and nothing more after that. > The cause seems to be in the fact that these notifications depend on the {{jboss.mbean.server}} MSC service, but that doesn't exist in admin-only mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2141) JMX notifications for ControlledProcessState changes are not updated when the running mode changes

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2141?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet updated WFCORE-2141: -------------------------------------- Description: When notifications are active and the server gets reloaded into admin-only mode we still have notifications to 'normal' mode. (was: JMX notifications added by https://issues.jboss.org/browse/EAP7-471 are not sent in admin-only mode. When notifications are active and the server gets reloaded into admin-only mode, only the normal->stopping transition is received and nothing more after that. The cause seems to be in the fact that these notifications depend on the {{jboss.mbean.server}} MSC service, but that doesn't exist in admin-only mode.) > JMX notifications for ControlledProcessState changes are not updated when the running mode changes > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-2141 > URL: https://issues.jboss.org/browse/WFCORE-2141 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > When notifications are active and the server gets reloaded into admin-only mode we still have notifications to 'normal' mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2016