[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2563:
--------------------------------
Fix Version/s: 7.14.0.Final
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[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 commented on JGRP-2312:
--------------------------------
[~dan.berindei] At TP initialization, cluster name and address may not yet be known, so I create a thread name "thread-<ADDR>-<CLUSTER>", and the 2 vars are replaced by the actual address and cluster name when connect() returns.
I could possibly grab all threads (via JMX) and rename them accordingly, but I'd rather only rename JGroups threads.
[~william.burns] How about, I remove all TERMINATED threads on after each LazyThreadFactory.newThread()? I don't think there's a callback that gets called when a thread is terminated.
> 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, 6 months
[JBoss JIRA] (DROOLS-3242) [Scenario Simulation] All grid cell editing should respond to single click
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3242?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-3242:
--------------------------------------
Assignee: Daniele Zonca (was: Michael Anstis)
> [Scenario Simulation] All grid cell editing should respond to single click
> ---------------------------------------------------------------------------
>
> Key: DROOLS-3242
> URL: https://issues.jboss.org/browse/DROOLS-3242
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Ivo Bek
> Assignee: Daniele Zonca
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click.
> h2. Manual Acceptance Test
> - Not possible edit multiple cells by hold CTRL and click on multiple cells
> - Click column/row leading cell discard edit dialog
> - Edit can be discarded by escape
> - Edit can be discarded by click to canvas
> - Invoke edit of cell
> - Save and reopen
> - Undo redo of editation
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months