October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type - Function parameter is simple data type - Multiple parameters was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type > - Function parameter is simple data type > - Multiple parameters -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] was:Our "Function Grid" does not support data-types for parameters... it should! > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11264) The BatchJobExecutionResource.hasChild() needs to be reviewed for purged jobs

by James Perkins (Jira)

James Perkins created WFLY-11264: ------------------------------------ Summary: The BatchJobExecutionResource.hasChild() needs to be reviewed for purged jobs Key: WFLY-11264 URL: https://issues.jboss.org/browse/WFLY-11264 Project: WildFly Issue Type: Bug Components: Batch Reporter: James Perkins Assignee: Cheng Fang The {{BatchJobExecutionResource.hasChild()}} invokes the {{hasJobExecution()}} method which does not by default refresh the children. This could mean that a purged job returns {{true}} when it should be {{false}}. This was originally done for performance reasons however there is a bug (WFLY-11261) which causes issues when a job is purged. In general this resource should be reviewed and performance tested to ensure purged jobs no longer show up. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11146) org.apache.activemq.artemis.journal module should not depend on org.apache.activemq.artemis

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11146?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFLY-11146: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > org.apache.activemq.artemis.journal module should not depend on org.apache.activemq.artemis > ------------------------------------------------------------------------------------------- > > Key: WFLY-11146 > URL: https://issues.jboss.org/browse/WFLY-11146 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Jeff Mesnil > Assignee: ehsavoie Hugonnet > Priority: Major > > While looking at Weld dependency, Jean-Francois found the dependency chain: > /org.jboss.as.weld/org.jboss.weld.core/javax.ejb.api/javax.rmi.api/javax.orb.api/org.wildfly.iiop-openjdk/org.jboss.jts/org.apache.activemq.artemis.journal/org.apache.activemq.artemis > org.jboss.jts dependency to org.apache.activemq.artemis.journal is correct as Naryana uses Artemis journal for its transaction log. > However org.apache.activemq.artemis.journal should not depend on org.apache.activemq.artemis. It depends on it for the artemis-commons jar (as explained in https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... but code should be refactored so that this dependency is no longer required). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11106) Kabir Test(For demo)

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11106?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11106: ------------------------------ Labels: EAP-CD15 EAP-CD16 EAP-CD17 (was: ) > Kabir Test(For demo) > -------------------- > > Key: WFLY-11106 > URL: https://issues.jboss.org/browse/WFLY-11106 > Project: WildFly > Issue Type: Feature Request > Components: Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > Labels: EAP-CD15, EAP-CD16, EAP-CD17 > > An issue for me to move around the board to test the tooling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-208) Missing -Djava.util.logging.manager=org.jboss.logmanager.LogManager for tests on IBM JDK

by Nikoleta Žiaková (Jira)

Nikoleta Žiaková created LOGMGR-208: --------------------------------------- Summary: Missing -Djava.util.logging.manager=org.jboss.logmanager.LogManager for tests on IBM JDK Key: LOGMGR-208 URL: https://issues.jboss.org/browse/LOGMGR-208 Project: JBoss Log Manager Issue Type: Bug Affects Versions: 2.1.5.Final Reporter: Nikoleta Žiaková There are several test failures on IBM JDK with following error: {quote} The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") {quote} This is similar to WFCORE-3797 but profile for IBM cannot be added since Maven is run with different JDK than the tests themselves - build requires JDK11 and the tests are run on IBM JDK 1.8 using {{java8.home}} property. Simple fix is to add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to surefire argLine like at https://github.com/nziakova/jboss-logmanager/commit/ae67e8b517866b80f7797... [~jamezp] WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1382) Destroy managed connection on failed reconnect

by Martin Simka (Jira)

[ https://issues.jboss.org/browse/JBJCA-1382?page=com.atlassian.jira.plugin... ] Martin Simka commented on JBJCA-1382: ------------------------------------- [~mitul.vora] version 1.4.12 containing this fix has not yet been released. When it is you download it from maven repository. Of course you can build it yourself from sources (https://github.com/ironjacamar/ironjacamar/). > Destroy managed connection on failed reconnect > ---------------------------------------------- > > Key: JBJCA-1382 > URL: https://issues.jboss.org/browse/JBJCA-1382 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Brad Maxwell > Assignee: Stefano Maestri > Priority: Major > > Destroy managed connection on failed reconnect -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1382) Destroy managed connection on failed reconnect

by Martin Simka (Jira)

[ https://issues.jboss.org/browse/JBJCA-1382?page=com.atlassian.jira.plugin... ] Martin Simka edited comment on JBJCA-1382 at 10/31/18 11:01 AM: ---------------------------------------------------------------- [~mitul.vora] version 1.4.12 containing this fix has not yet been released. When it is you can download it from maven repository. Of course you can build it yourself from sources (https://github.com/ironjacamar/ironjacamar/). was (Author: simkam): [~mitul.vora] version 1.4.12 containing this fix has not yet been released. When it is you download it from maven repository. Of course you can build it yourself from sources (https://github.com/ironjacamar/ironjacamar/). > Destroy managed connection on failed reconnect > ---------------------------------------------- > > Key: JBJCA-1382 > URL: https://issues.jboss.org/browse/JBJCA-1382 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Brad Maxwell > Assignee: Stefano Maestri > Priority: Major > > Destroy managed connection on failed reconnect -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3107) Provide optional lazy segment memories creation

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3107?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-3107. --------------------------------- Fix Version/s: 7.14.0.Final Resolution: Done Implemented by https://github.com/kiegroup/drools/commit/2a3a8aa138a9e8022b24e280d7f7e99... > Provide optional lazy segment memories creation > ----------------------------------------------- > > Key: DROOLS-3107 > URL: https://issues.jboss.org/browse/DROOLS-3107 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Fix For: 7.14.0.Final > > > The execution of the very first ksession created from a kbase is (much) slower than the subsequent ones, because of lazy segment memories creation. It is requested to provide an option to eagerly create them at kbase creation time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018