March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1337) Provide capabilities for paths

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1337?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1337: ------------------------------------- Issue Type: Enhancement (was: Task) > Provide capabilities for paths > ------------------------------ > > Key: WFCORE-1337 > URL: https://issues.jboss.org/browse/WFCORE-1337 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > We need to be able to do reference validation for capabilities to avoid problems like WFCORE-1333. > This is going to take careful thought though. The PathManager is a bit of a complex beast. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include "exists" elements too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1474?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1474: ------------------------------------------ Note that it doesn't make sense to include "not" elements in getObjectsDeep(), including "not exists" (which is the same basically), because they aren't to blame for the rule matching (or all facts are to blame, so that would be pointless too). > Activation.getObjectsDeep() should include "exists" elements too > ---------------------------------------------------------------- > > Key: DROOLS-1474 > URL: https://issues.jboss.org/browse/DROOLS-1474 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) > The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: > {code} > when > $c : Computer(id = "c1") > exists Process(computer == $c) > then ... > {code} > with this data > {code} > Computer c1; > Computer c2; > Computer c3; > Process pA = new Process(c1); > Process pB = new Process(c2); > Process pC = new Process(c1); > Process pD = new Process(c3); > {code} > gives this result > {code} > activation.getObjectsDeep() // includes c1, pA and pC. > {code} > The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include "exists" elements too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1474?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1474: ------------------------------------- Summary: Activation.getObjectsDeep() should include "exists" elements too (was: Activation.getObjectsDeep() should include exists too) > Activation.getObjectsDeep() should include "exists" elements too > ---------------------------------------------------------------- > > Key: DROOLS-1474 > URL: https://issues.jboss.org/browse/DROOLS-1474 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) > The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: > {code} > when > $c : Computer(id = "c1") > exists Process(computer == $c) > then ... > {code} > with this data > {code} > Computer c1; > Computer c2; > Computer c3; > Process pA = new Process(c1); > Process pB = new Process(c2); > Process pC = new Process(c1); > Process pD = new Process(c3); > {code} > gives this result > {code} > activation.getObjectsDeep() // includes c1, pA and pC. > {code} > The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include exists too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1474?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1474: ------------------------------------- Description: _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: {code} when $c : Computer(id = "c1") exists Process(computer == $c) then ... {code} with this data {code} Computer c1; Computer c2; Computer c3; Process pA = new Process(c1); Process pB = new Process(c2); Process pC = new Process(c1); Process pD = new Process(c3); {code} gives this result {code} activation.getObjectsDeep() // includes c1, pA and pC. {code} The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. was: _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: {code} when $c : Computer(id = "c1") exists Process(computer == $c) then ... {code} with this data {code} Computer c1; Computer c2; Computer c3; Process pA = new Process(c1); Process pB = new Process(c2); Process pC = new Process(c1); Process pD = new Process(c3); {code} gives this result {code} activation.getObjectsDeep() // includes c1, pA and pC. {code} The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. > Activation.getObjectsDeep() should include exists too > ----------------------------------------------------- > > Key: DROOLS-1474 > URL: https://issues.jboss.org/browse/DROOLS-1474 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) > The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: > {code} > when > $c : Computer(id = "c1") > exists Process(computer == $c) > then ... > {code} > with this data > {code} > Computer c1; > Computer c2; > Computer c3; > Process pA = new Process(c1); > Process pB = new Process(c2); > Process pC = new Process(c1); > Process pD = new Process(c3); > {code} > gives this result > {code} > activation.getObjectsDeep() // includes c1, pA and pC. > {code} > The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include exists too

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-1474: ---------------------------------------- Summary: Activation.getObjectsDeep() should include exists too Key: DROOLS-1474 URL: https://issues.jboss.org/browse/DROOLS-1474 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.0.0.Beta6 Reporter: Geoffrey De Smet Assignee: Mario Fusco _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb) The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example: {code} when $c : Computer(id = "c1") exists Process(computer == $c) then ... {code} with this data {code} Computer c1; Computer c2; Computer c3; Process pA = new Process(c1); Process pB = new Process(c2); Process pC = new Process(c1); Process pD = new Process(c3); {code} gives this result {code} activation.getObjectsDeep() // includes c1, pA and pC. {code} The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8341) Custom externalizer for ZoneOffset is ignored

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8341?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-9504 to WFLY-8341: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8341 (was: JBEAP-9504) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR13) > Custom externalizer for ZoneOffset is ignored > --------------------------------------------- > > Key: WFLY-8341 > URL: https://issues.jboss.org/browse/WFLY-8341 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > This externalizer class is missing from the generated /META-INF/services/org.wildfly.clustering.marshalling.Externalizer resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1337) Provide capabilities for paths

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1337?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1337: ---------------------------------------- Assignee: Brian Stansberry > Provide capabilities for paths > ------------------------------ > > Key: WFCORE-1337 > URL: https://issues.jboss.org/browse/WFCORE-1337 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > We need to be able to do reference validation for capabilities to avoid problems like WFCORE-1333. > This is going to take careful thought though. The PathManager is a bit of a complex beast. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1337) Provide capabilities for paths

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1337?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1337: ------------------------------------- Fix Version/s: (was: 4.0.0.Beta1) > Provide capabilities for paths > ------------------------------ > > Key: WFCORE-1337 > URL: https://issues.jboss.org/browse/WFCORE-1337 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > > We need to be able to do reference validation for capabilities to avoid problems like WFCORE-1333. > This is going to take careful thought though. The PathManager is a bit of a complex beast. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1703) JVM resource handling of jvm-options should detect -D options and integrate with system-property logic

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1703?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1703: ------------------------------------- Issue Type: Enhancement (was: Bug) > JVM resource handling of jvm-options should detect -D options and integrate with system-property logic > ------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1703 > URL: https://issues.jboss.org/browse/WFCORE-1703 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 2.2.0.Final > Reporter: Bogdan Ilchyshyn > Priority: Minor > Labels: domain-mode > > It is not possible to set {{jboss.modules.system.pkgs}} property per server / server group in domain configuration. Even when the following configuration is added to {{host.xml}}: > {code:xml} > <server name="server-one" group="main-server-group"> > <jvm name="default"> > <jvm-options> > <option value="-Djboss.modules.system.pkgs=my.package"/> > ... > {code} > It is overridden by configuration in {{domain.conf}}: > {noformat} > JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" > {noformat} > This is an issue for configuring third-party java agents per-server. A problem described in WFLY-895 adds to this. One should either add a whole bunch of things to _all_ jvms in domain in order to make agent work, or remove config from {{domain.conf}} to avoid overrides. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8336) Upgrade Narayana to 5.5.5.Final

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-8336?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-8336: -------------------------------- Description: https://issues.jboss.org/projects/JBTM/versions/12333853 https://issues.jboss.org/projects/JBTM/versions/12334095 https://github.com/jbosstm/narayana/compare/5.5.3.Final...5.5.5.Final was: https://issues.jboss.org/projects/JBTM/versions/12333853 https://github.com/jbosstm/narayana/compare/5.5.3.Final...5.5.4.Final > Upgrade Narayana to 5.5.5.Final > ------------------------------- > > Key: WFLY-8336 > URL: https://issues.jboss.org/browse/WFLY-8336 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > https://issues.jboss.org/projects/JBTM/versions/12333853 > https://issues.jboss.org/projects/JBTM/versions/12334095 > https://github.com/jbosstm/narayana/compare/5.5.3.Final...5.5.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017