March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1849) Guided decision table: Require the ability to hide facts

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1849?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1849. ------------------------------- Resolution: Rejected Closing this issue as there were no resources to address it for a long time, moreover with the changed team priorities (it is DMN now) is even less probable to find resources for this issue. > Guided decision table: Require the ability to hide facts > -------------------------------------------------------- > > Key: DROOLS-1849 > URL: https://issues.jboss.org/browse/DROOLS-1849 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > Priority: Major > > I would like to have control over what facts are available to a decision table in Guvnor. > We may have facts A, B, and C and Decision Tables 1 and 2. We want to be able to configure Decision Table 1 to only see facts A and for Decision Table 2 to see facts B & C. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1850) Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1850?page=com.atlassian.jira.plugi... ] Jozef Marko reopened DROOLS-1850: --------------------------------- > Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions > ------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1850 > URL: https://issues.jboss.org/browse/DROOLS-1850 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > Priority: Major > > I would like to have the control to hide or display properties that are exposed as conditions and actions in guvnor. I have a utility class that calculates a number for a condition check but when configured in the decision table it is selectable as an action property but I only want it configured for a condition. > Public Class A { > // Show the following method as a condition property and not an action property > public int calculateNumber() { > do some calculation.. > return results. > } > // Show the following method as a condition property and not an action and property > public BigDecimal getBalance() { > return balance > } > // Show the following method as a action property and not an condition property > public void assignValue(String value) { > this.value = value; > } > } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1850) Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1850?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1850. ------------------------------- Resolution: Rejected > Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions > ------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1850 > URL: https://issues.jboss.org/browse/DROOLS-1850 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > Priority: Major > > I would like to have the control to hide or display properties that are exposed as conditions and actions in guvnor. I have a utility class that calculates a number for a condition check but when configured in the decision table it is selectable as an action property but I only want it configured for a condition. > Public Class A { > // Show the following method as a condition property and not an action property > public int calculateNumber() { > do some calculation.. > return results. > } > // Show the following method as a condition property and not an action and property > public BigDecimal getBalance() { > return balance > } > // Show the following method as a action property and not an condition property > public void assignValue(String value) { > this.value = value; > } > } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1850) Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1850?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1850. ------------------------------- Resolution: Done Closing this issue as there were no resources to address it for a long time, moreover with the changed team priorities (it is DMN now) is even less probable to find resources for this issue. > Guided decision table: Add meta-data to control which fact properties are exposed when configuring conditions or actions > ------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-1850 > URL: https://issues.jboss.org/browse/DROOLS-1850 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Reporter: Ed Wallen > Assignee: Michael Anstis > Priority: Major > > I would like to have the control to hide or display properties that are exposed as conditions and actions in guvnor. I have a utility class that calculates a number for a condition check but when configured in the decision table it is selectable as an action property but I only want it configured for a condition. > Public Class A { > // Show the following method as a condition property and not an action property > public int calculateNumber() { > do some calculation.. > return results. > } > // Show the following method as a condition property and not an action and property > public BigDecimal getBalance() { > return balance > } > // Show the following method as a action property and not an condition property > public void assignValue(String value) { > this.value = value; > } > } -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11903) Deployment failure if existing HA deployment contains a common EJB class

by Brad Maxwell (Jira)

[ https://issues.jboss.org/browse/WFLY-11903?page=com.atlassian.jira.plugin... ] Brad Maxwell reassigned WFLY-11903: ----------------------------------- Assignee: JBoss SET (was: Paul Ferraro) > Deployment failure if existing HA deployment contains a common EJB class > ------------------------------------------------------------------------ > > Key: WFLY-11903 > URL: https://issues.jboss.org/browse/WFLY-11903 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Brad Maxwell > Assignee: JBoss SET > Priority: Major > Fix For: 7.2.2.GA > > > Currently, the command dispatcher ID uses the bean name. This needs to be qualified using the deployment name. > {noformat}Thrown in org.wildfly.clustering.server.dispatcher.MangedCommandDispatcherFactory.cre>ateCommandDispatcher(Object id, C context) line 98 "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefullBean.START" => "java.lang.Ille galArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean alrea dy exists, but with a different command context", > slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefulBean2.START" => "java.lang.IllegalA rgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already e xists, but with a different command context" > slave1 | [Server:group1] }, > slave1 | [Server:group1] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { > slave1 | [Server:group1] "Services that were unable to start:" => [ slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".moduleDeploymentRuntimeInformationStart", slave1 | [Server:group1] "jboss.deployment.unit.\"app2.ear\".WeldEndInitService", slave1 | [Server:group1] "jboss.undertow.deployment.default-server.default-host./app2" > slave1 | [Server:group1] ], slave1 | [Server:group1] "Services that may be the cause:" => ` > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11903) Deployment failure if existing HA deployment contains a common EJB class

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-11903: ----------------------------------- Summary: Deployment failure if existing HA deployment contains a common EJB class Key: WFLY-11903 URL: https://issues.jboss.org/browse/WFLY-11903 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 14.0.0.Final Reporter: Brad Maxwell Assignee: Paul Ferraro Fix For: 15.0.0.Beta1, 15.0.0.Final Currently, the command dispatcher ID uses the bean name. This needs to be qualified using the deployment name. {noformat}Thrown in org.wildfly.clustering.server.dispatcher.MangedCommandDispatcherFactory.cre>ateCommandDispatcher(Object id, C context) line 98 "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefullBean.START" => "java.lang.Ille galArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean alrea dy exists, but with a different command context", slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefulBean2.START" => "java.lang.IllegalA rgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already e xists, but with a different command context" slave1 | [Server:group1] }, slave1 | [Server:group1] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { slave1 | [Server:group1] "Services that were unable to start:" => [ slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".moduleDeploymentRuntimeInformationStart", slave1 | [Server:group1] "jboss.deployment.unit.\"app2.ear\".WeldEndInitService", slave1 | [Server:group1] "jboss.undertow.deployment.default-server.default-host./app2" slave1 | [Server:group1] ], slave1 | [Server:group1] "Services that may be the cause:" => ` {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11902) Deprecated configuration for TCPGOSSIP not usable

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11902?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFLY-11902. ------------------------------- Resolution: Rejected The num_initial_members property was deprecated in JGroups 3.5.0.Final (i.e. since WF9), so users were amply warned that this property would be removed in a future release. In general, informal JGroups properties are not part of the formal management model (unlike those properties that correspond to formal attributes) and thus are not subject to compatibility requirements as suggested by this jira. > Deprecated configuration for TCPGOSSIP not usable > ------------------------------------------------- > > Key: WFLY-11902 > URL: https://issues.jboss.org/browse/WFLY-11902 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Richard Janík > Assignee: Paul Ferraro > Priority: Critical > > Related to WFLY-11901. Found on current master. > Running the example files produces: > {code} > ./standalone.sh -Djboss.jgroups.gossip.initial_hosts=127.0.0.1[12004] -Djboss.jgroups.gossip.num_initial_members=1 --server-config=../../docs/examples/configs/standalone-gossip-full-ha.xml > 12:49:01,924 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 84) MSC000001: Failed to start service org.wildfly.clustering.jgroups.channel.ee: org.jboss.msc.service.StartException in service org.wildfly.clustering.jgroups.channel.ee: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:70) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: java.lang.IllegalStateException: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:116) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:58) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:67) > ... 7 more > Caused by: java.lang.IllegalArgumentException: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:130) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:106) > at org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.get(ChannelServiceConfigurator.java:96) > ... 9 more > Caused by: java.security.PrivilegedActionException: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:851) > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.createProtocol(AbstractProtocolConfigurationServiceConfigurator.java:125) > ... 11 more > Caused by: java.lang.IllegalArgumentException: Unrecognized TCPGOSSIP properties: [num_initial_members] > at org.jgroups.stack.Protocol.setProperties(Protocol.java:144) > at org.jboss.as.clustering.jgroups.subsystem.AbstractProtocolConfigurationServiceConfigurator.lambda$createProtocol$0(AbstractProtocolConfigurationServiceConfigurator.java:119) > at org.wildfly.security.manager.WildFlySecurityManager.doUnchecked(WildFlySecurityManager.java:849) > ... 12 more > {code} > Even though the configuration in the examples is deprecated, it should still work as changes between minor versions should be backward compatible. While this incompatibility is fine for WFLY, it is an issue for the product, where 17.0 will only translate to a minor version update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11897) SFSB expiration failures cause memory leak

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-11897: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12183 (was: https://issues.jboss.org/browse/WFLY-11897) > SFSB expiration failures cause memory leak > ------------------------------------------ > > Key: WFLY-11897 > URL: https://issues.jboss.org/browse/WFLY-11897 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Major > Attachments: WFLY-11897.btm, test.ear > > > There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11897) SFSB expiration failures cause memory leak

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11897?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-11897: -------------------------------- Summary: SFSB expiration failures cause memory leak (was: SFSB expiration can fail) > SFSB expiration failures cause memory leak > ------------------------------------------ > > Key: WFLY-11897 > URL: https://issues.jboss.org/browse/WFLY-11897 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Dennis Reed > Assignee: Paul Ferraro > Priority: Major > Attachments: WFLY-11897.btm, test.ear > > > There is a timing bug where SFSB expiration can run while the SFSB is still locked, causing the expiration to fail and never retry, leaving the SFSB active indefinitely. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3747) KNative + Quarkus Drools/jBPM demo

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3747?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3747: ----------------------------------- Sprint: (was: 2019 Week 11-13) > KNative + Quarkus Drools/jBPM demo > ---------------------------------- > > Key: DROOLS-3747 > URL: https://issues.jboss.org/browse/DROOLS-3747 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > Try and setup a small, limited knative demo with either drools or jbpm using quarkus to expose an endpoint > Expected deliverable: a github repository with scripts to start the demo on minishift/minikube -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019