January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3447) Remove "DMN Asset" dependency from TitledAttachmentFileWidget

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3447?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-3447: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Remove "DMN Asset" dependency from TitledAttachmentFileWidget > ------------------------------------------------------------- > > Key: DROOLS-3447 > URL: https://issues.redhat.com/browse/DROOLS-3447 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > > Currently, TitledAttachmentFileWidget use ProjectAssetsQuery to retrieve the "dmn" files. > Implicitly, this means that *if* (for whatever reason) dmn editor is disabled, the dmn file are not retrieved. Wording differently, this creates an implicit dependency between scenariosimulation and dmn editor. > Fix it so that TitledAttachmentFileWidget could find dmn files regardless of dmn editor. > Look at left dock that shows all the files of the project. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4720) Use Objects.equals in AbstractScesimData

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4720?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4720: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Use Objects.equals in AbstractScesimData > ---------------------------------------- > > Key: DROOLS-4720 > URL: https://issues.redhat.com/browse/DROOLS-4720 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > We should use _Objects.equals()_ instead of simple _equals_ in the [AbstractScesimData|https://github.com/kiegroup/drools/blob/b1bc7ebb290604...] class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4727: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2417) Ref-counting for messages

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2417?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2417: --------------------------- Description: When users do their own memory management, the message passed to {{Channel.send()}} might have a reference to a memory area that's allocated from a pool, and that needs to be returned when done. However, the return of a {{Channel.send()}} call does not necessarily mean that the memory area can be reused. If, for example, NAKACK2 or UNICAST3 have the message in their retransmission tables (to potentially retransmit it), then the memory cannot be reused until that message has been purged from the retransmission table. Add a reference-counting mechanism to {{Message}} (implemented in {{BaseMessage}}) that allows NAKACK2 or UNICAST3 to increment a ref-count. When a message is purged from the retransmission table, decrement its ref-count. When the ref-count is 0, a callback could be called. The callback could for example return the associated memory chunk back to the memory pool. This could possibly be a trait, with a no-op implementation as default. This could be overwritten, ie. {code:java} Message release() { if(refcount <= 0) // give associated memory area back to pool } {code} See if this needs to be integrated with {{MessageFactory}} as well. was: When users do their own memory management, the message passed to {{Channel.send()}} might have a reference to a memory area that's allocated from a pool, and that needs to be returned when done. However, {{Channel.send()}} does not necessarily mean that the memory area can be reused. If, for example, NAKACK2 or UNICAST3 have the message in their retransmission tables (to potentially retransmit it), then the memory cannot be reused until that message has been purged from the retransmission table. Add a reference-counting mechanism to {{Message}} (implemented in {{BaseMessage}}) that allows NAKACK2 or UNICAST3 to increment a ref-count. When a message is purged from the retransmission table, decrement its ref-count. When the ref-count is 0, a callback could be called. The callback could for example return the associated memory chunk back to the memory pool. This could possibly be a trait, with a no-op implementation as default. This could be overwritten, ie. {code:java} Message release() { if(refcount <= 0) // give associated memory area back to pool } {code} See if this needs to be integrated with {{MessageFactory}} as well. > Ref-counting for messages > ------------------------- > > Key: JGRP-2417 > URL: https://issues.redhat.com/browse/JGRP-2417 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > When users do their own memory management, the message passed to {{Channel.send()}} might have a reference to a memory area that's allocated from a pool, and that needs to be returned when done. > However, the return of a {{Channel.send()}} call does not necessarily mean that the memory area can be reused. If, for example, NAKACK2 or UNICAST3 have the message in their retransmission tables (to potentially retransmit it), then the memory cannot be reused until that message has been purged from the retransmission table. > Add a reference-counting mechanism to {{Message}} (implemented in {{BaseMessage}}) that allows NAKACK2 or UNICAST3 to increment a ref-count. When a message is purged from the retransmission table, decrement its ref-count. When the ref-count is 0, a callback could be called. The callback could for example return the associated memory chunk back to the memory pool. > This could possibly be a trait, with a no-op implementation as default. This could be overwritten, ie. > {code:java} > Message release() { > if(refcount <= 0) > // give associated memory area back to pool > } > {code} > See if this needs to be integrated with {{MessageFactory}} as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4671) Scenario Grids keyboard control

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4671?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4671: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Scenario Grids keyboard control > ------------------------------- > > Key: DROOLS-4671 > URL: https://issues.redhat.com/browse/DROOLS-4671 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Scenario keyboard control needs to work immediately after opening Model or Background tab, see the [comment|https://github.com/kiegroup/drools-wb/pull/1239#discussion_r33638...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3315) Implement placeholder mechanism for the header of the grid

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-3315?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-3315: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Implement placeholder mechanism for the header of the grid > ---------------------------------------------------------- > > Key: DROOLS-3315 > URL: https://issues.redhat.com/browse/DROOLS-3315 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Yeser Amer > Priority: Minor > Labels: ScenarioSimulation, drools-tools > > Implement directly in core-grids an extension of placeholder mechanism to cover also the header -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4838) Create common producer for tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4838?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4838: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Create common producer for tests > -------------------------------- > > Key: DROOLS-4838 > URL: https://issues.redhat.com/browse/DROOLS-4838 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > > Inside the tests there is a whole bunch of mocked objects that are used in multiple places (especially the ones related to grid/cell/rendering stuff). > Scope of this ticket shuold be to put all of them inside a static producer; this would also reduce the needs for abstract/inheritance chains, simplifying the test environment -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4576?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4576: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Data object selector Search widget not enabled in saved tests > ------------------------------------------------------------- > > Key: DROOLS-4576 > URL: https://issues.redhat.com/browse/DROOLS-4576 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: 2019-09-27 13.36.19.gif > > > The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4721) Use Objects.equals in ScesimModelDescriptor

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4721?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4721: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Use Objects.equals in ScesimModelDescriptor > ------------------------------------------- > > Key: DROOLS-4721 > URL: https://issues.redhat.com/browse/DROOLS-4721 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > We should use _Objects.equals()_ instead of simple _equals_ in the [ScesimModelDescriptor|https://github.com/kiegroup/drools/blob/b1bc7ebb290...] class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4769) Add an empty row on grid when importing "empty" csv

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4769?page=com.atlassian.jira.plug... ] Gabriele Cardosi reassigned DROOLS-4769: ---------------------------------------- Assignee: Yeser Amer (was: Gabriele Cardosi) > Add an empty row on grid when importing "empty" csv > --------------------------------------------------- > > Key: DROOLS-4769 > URL: https://issues.redhat.com/browse/DROOLS-4769 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: DmnAssert.scesim, DmnAssert.scesim.csv, Driver Suspension Rules.dmn, image.png > > > If user import csv file in DMN scenario, which contains only header, then the Background contains no rows see [^image.png] > Steps to reproduce : > # Import [^Driver Suspension Rules.dmn] > # Import [^DmnAssert.scesim] > # In scesim file import [^DmnAssert.scesim.csv] > Expected: Grid with the cells state the same as after initialization > Actual: user has no rows to add a value > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

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 January 2020