January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4965?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4965: ----------------------------------- Fix Version/s: (was: 7.32.0.Final) Affects Version/s: 7.32.0.Final > [DMN Designer] Dragged structure fields nest in a counterintuitive way > ---------------------------------------------------------------------- > > Key: DROOLS-4965 > URL: https://issues.redhat.com/browse/DROOLS-4965 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Michael Anstis > Priority: Major > Attachments: drag-1.gif > > > Because the handle is aligned leftmost, I tend to keep it aligned to the left; > but this causes the field to be "unnested" and moved to toplevel. > I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point > !drag-1.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4965: -------------------------------------- Summary: [DMN Designer] Dragged structure fields nest in a counterintuitive way Key: DROOLS-4965 URL: https://issues.redhat.com/browse/DROOLS-4965 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Edoardo Vacchi Assignee: Michael Anstis Fix For: 7.32.0.Final Attachments: drag-1.gif Because the handle is aligned leftmost, I tend to keep it aligned to the left; but this causes the field to be "unnested" and moved to toplevel. I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point !drag-1.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4964) [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4964: -------------------------------------- Summary: [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked Key: DROOLS-4964 URL: https://issues.redhat.com/browse/DROOLS-4964 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: scroll-up.gif - scroll down - click on a non-active part of the table (i.e. not a button) result: the viewport scrolls up to the top !scroll-up.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4963: -------------------------------------- Summary: [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open Key: DROOLS-4963 URL: https://issues.redhat.com/browse/DROOLS-4963 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.32.0.Final Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: Screenshot from 2020-01-22 16-16-29.png, Screenshot from 2020-01-22 16-16-29.png hiding the inspector on the right-hand side uncovers the save/cancel buttons !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13006) KUBE_PING Occasional NPE on shutdown

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13006?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFLY-13006: --------------------------------------- Requires 1.0.15.Final upgrade. > KUBE_PING Occasional NPE on shutdown > ------------------------------------- > > Key: WFLY-13006 > URL: https://issues.redhat.com/browse/WFLY-13006 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > 05:52:55,313 ERROR [org.jgroups.util.TimeScheduler3] (thread-6,null,xa-load-2) JGRP000169: failed executing task MERGE3: InfoSender: java.lang.NullPointerException > at org.jgroups.protocols.kubernetes.KUBE_PING.readAll(KUBE_PING.java:313) > at org.jgroups.protocols.kubernetes.KUBE_PING.findMembers(KUBE_PING.java:206) > at org.jgroups.protocols.Discovery.invokeFindMembers(Discovery.java:216) > at org.jgroups.protocols.Discovery.findMembers(Discovery.java:241) > at org.jgroups.protocols.Discovery.down(Discovery.java:384) > at org.jgroups.protocols.MERGE3$InfoSender.run(MERGE3.java:413) > at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:328) > at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:362) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52) > at java.lang.Thread.run(Thread.java:748) > https://github.com/jgroups-extras/jgroups-kubernetes/issues/39 > https://github.com/jgroups-extras/jgroups-kubernetes/pull/88 > Will be resolved with a next jgroups-kubernetes upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2438?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2438. ---------------------------- Resolution: Done > MPerf: add -nohup option > ------------------------ > > Key: JGRP-2438 > URL: https://issues.redhat.com/browse/JGRP-2438 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0, 4.0.22 > > > Add -nohup option to MPerf -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2438?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2438: --------------------------- Description: Add -nohup option to MPerf Fix Version/s: 4.0.22 > MPerf: add -nohup option > ------------------------ > > Key: JGRP-2438 > URL: https://issues.redhat.com/browse/JGRP-2438 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0, 4.0.22 > > > Add -nohup option to MPerf -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

Bela Ban created JGRP-2438: ------------------------------ Summary: MPerf: add -nohup option Key: JGRP-2438 URL: https://issues.redhat.com/browse/JGRP-2438 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0, 4.2.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4936) Unsaved changes dialog appears even if it just have been saved

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4936?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4936: -------------------------------- Tester: Anna Dupliak > Unsaved changes dialog appears even if it just have been saved > -------------------------------------------------------------- > > Key: DROOLS-4936 > URL: https://issues.redhat.com/browse/DROOLS-4936 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Open a GRE file. Add a fact pattern. Save. > Close and the editor still thinks it has not been saved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13007) New subsystem for configuring clustering API implementations

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13007?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13007: -------------------------------- Description: Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary * Simplifies inter-component capability requirements (e.g. SingletonServiceConfiguratorFactory depends on ServiceProviderRegistry and CommandDispatcherFactory). was: Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary > New subsystem for configuring clustering API implementations > ------------------------------------------------------------ > > Key: WFLY-13007 > URL: https://issues.redhat.com/browse/WFLY-13007 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Currently, WildFly creates services for the following objects for every JGroups channel: > * CommandDispatcherFactory > * Group > ... and creates services the following objects for every Infinispan cache: > * SingletonServiceConfiguratorFactory > * ServiceProviderRegistry > * Registry > * Group > Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. > This has a number of benefits for users as well: > * Increases overall visibility of the public clustering API > * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary > * Simplifies inter-component capability requirements (e.g. SingletonServiceConfiguratorFactory depends on ServiceProviderRegistry and CommandDispatcherFactory). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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