October 2018 - jboss-jira - Jboss List Archives

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

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3214: -------------------------------------- Summary: [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 Our "Function Grid" does not support data-types for parameters... it should! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3213) Remove readOnly property from ScenarioGridColumn

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3213: ---------------------------------------- Summary: Remove readOnly property from ScenarioGridColumn Key: DROOLS-3213 URL: https://issues.jboss.org/browse/DROOLS-3213 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Inside ScenarioGridColumn there is a "readOnly" flag with public accessors (getter/setter). Remove the property and the setter. Let the "gettert" evaluate at runtime based on: type (Index/description/given/expected; if Index -> always true (redOnly) if description ->A always false (= *not readonly) if given/expected: depends on isInstanceAssigned/isPropertyAssigned -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3111) [DMN Designer] Decision table generation fails if custom input data connected

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3111?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3111: -------------------------------- Description: The decision table generation according to connected input data nodes fails if some custom input data is connected. h2. Manual acceptance test Check when connected input data is of type: - Built in data type - Custom data type, just alias for Built in type - Custom data type, structure - Custom data type, structure containing another structure - Custom data type, just alias for structure was:The decision table generation according to connected input data nodes fails if some custom input data is connected. > [DMN Designer] Decision table generation fails if custom input data connected > ----------------------------------------------------------------------------- > > Key: DROOLS-3111 > URL: https://issues.jboss.org/browse/DROOLS-3111 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: a1.dmn, aaa.dmn > > > The decision table generation according to connected input data nodes fails if some custom input data is connected. > h2. Manual acceptance test > Check when connected input data is of type: > - Built in data type > - Custom data type, just alias for Built in type > - Custom data type, structure > - Custom data type, structure containing another structure > - Custom data type, just alias for structure -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2312) LazyThreadFactory can keep threads instances alive for a long period

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2312?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2312: --------------------------- Fix Version/s: 4.0.16 > LazyThreadFactory can keep threads instances alive for a long period > -------------------------------------------------------------------- > > Key: JGRP-2312 > URL: https://issues.jboss.org/browse/JGRP-2312 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.15 > Reporter: William Burns > Assignee: Bela Ban > Priority: Major > Fix For: 4.0.16 > > > The LazyThreadFactory keeps all Thread objects in a ConcurrentLinkedQueue wrapped by a WeakReference. This means that once a thread terminates, its instance along with all native memory required for it can linger until the GC eventually reclaims it. Normally this is not an issue when the JVM heap is being recycled often, but in cases where you have low heap requirement operations (ie. off heap data container) this can cause these objects to pile up and eventually exhaust native memory. > This queue is also a very slow JVM heap leak as threads are tossed out, since the WeakReference and Queue Node objects are never reclaimed unless the transport is stopped. > The best way to fix this would be to plug into when the thread is set to TERMINATED state and to remove these nodes. > Also a workaround is to increase the core thread count and increase the keepalive timeout so that threads are not destroyed and created nearly as often. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10684) Upgrade Yasson to 1.0.2

by Erik . (Jira)

[ https://issues.jboss.org/browse/WFLY-10684?page=com.atlassian.jira.plugin... ] Erik . commented on WFLY-10684: ------------------------------- Eclipse closed issue and released 1.0.2 finally on maven central repository. With the update to the pom.xml in the master branch I think this issue can be closed > Upgrade Yasson to 1.0.2 > ----------------------- > > Key: WFLY-10684 > URL: https://issues.jboss.org/browse/WFLY-10684 > Project: WildFly > Issue Type: Component Upgrade > Components: EE, REST > Affects Versions: 13.0.0.Final, 14.0.0.Final > Reporter: Erik . > Assignee: Alessio Soldano > Priority: Critical > Fix For: 15.0.0.Alpha1 > > > Upgrade to Eclipse Yasson from 1.0.1 to 1.0.2 to fix https://github.com/eclipse-ee4j/yasson/issues/137 > The implementation for PropertyVisibilityStrategy for fields does not work as it should. @JsonbProperty() on private fields does not work as mentioned on page 17 of the Json-B 1.0: Java™ API for JSON Binding published on May 15th 2017. > 1.0.2 will be released somewhere week -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7419) Include RESTEasy WADL module

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-7419?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-7419: -------------------------------- Issue Type: Feature Request (was: Enhancement) > Include RESTEasy WADL module > ---------------------------- > > Key: WFLY-7419 > URL: https://issues.jboss.org/browse/WFLY-7419 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Frank Langelage > Assignee: Weinan Li > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3211) [DMN Designer] Marshaller: Conversion from 1.1 to 1.2 leads to 'Unable to resolve type reference' errors

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3211?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3211: -------------------------------------- Assignee: Michael Anstis (was: Matteo Mortari) > [DMN Designer] Marshaller: Conversion from 1.1 to 1.2 leads to 'Unable to resolve type reference' errors > -------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3211 > URL: https://issues.jboss.org/browse/DROOLS-3211 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Following the discussion on https://issues.jboss.org/browse/DROOLS-3038?focusedCommentId=13654791&pag... (opening a 1.1 file, saving, leading to lots of 'Unable to resolve type reference' errors for built-in types. > On investigation it appears a lot of our backend marshaller tests are also reporting the error following conversion from 1.1 to 1.2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3211) [DMN Designer] Marshaller: Conversion from 1.1 to 1.2 leads to 'Unable to resolve type reference' errors

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3211?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-3211: -------------------------------------- Assignee: Matteo Mortari (was: Michael Anstis) > [DMN Designer] Marshaller: Conversion from 1.1 to 1.2 leads to 'Unable to resolve type reference' errors > -------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3211 > URL: https://issues.jboss.org/browse/DROOLS-3211 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Matteo Mortari > Priority: Blocker > Labels: drools-tools > > Following the discussion on https://issues.jboss.org/browse/DROOLS-3038?focusedCommentId=13654791&pag... (opening a 1.1 file, saving, leading to lots of 'Unable to resolve type reference' errors for built-in types. > On investigation it appears a lot of our backend marshaller tests are also reporting the error following conversion from 1.1 to 1.2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2926) Make the old panel reusable (move to kie-wb-common-ui) and use it on both old and new test scenarios

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2926?page=com.atlassian.jira.plugi... ] Toni Rikkola resolved DROOLS-2926. ---------------------------------- Resolution: Done > Make the old panel reusable (move to kie-wb-common-ui) and use it on both old and new test scenarios > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-2926 > URL: https://issues.jboss.org/browse/DROOLS-2926 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3212) Scenario simulation can not be closed without a warning if it has been ran

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-3212: ------------------------------------ Summary: Scenario simulation can not be closed without a warning if it has been ran Key: DROOLS-3212 URL: https://issues.jboss.org/browse/DROOLS-3212 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Toni Rikkola Assignee: Daniele Zonca The problem is caused by the fact that running the simulation updates the model. Steps to reproduce: Open scesim asset. Run the scenario. Close the editor You get a warning that there are unsaved changes. -- 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