March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5125) [DMN Designer] Node data type is lost after drag and drop in data type editor

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5125?page=com.atlassian.jira.plug... ] Daniel José dos Santos updated DROOLS-5125: ------------------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) > [DMN Designer] Node data type is lost after drag and drop in data type editor > ----------------------------------------------------------------------------- > > Key: DROOLS-5125 > URL: https://issues.redhat.com/browse/DROOLS-5125 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > > In dmn diagram, each nodes has its data type. The issue affects all nodes, after reordering custom defined data types. After such reordering data types of diagram nodes are lost. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5125) [DMN Designer] Node data type is lost after drag and drop in data type editor

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-5125?page=com.atlassian.jira.plug... ] Daniel José dos Santos moved RHDM-1282 to DROOLS-5125: ------------------------------------------------------ Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-5125 (was: RHDM-1282) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: DMN Editor (was: Decision Central) Affects Build: (was: CR1) Affects Version/s: (was: 7.6.0.GA) (was: 7.7.0.GA) QE Status: NEW > [DMN Designer] Node data type is lost after drag and drop in data type editor > ----------------------------------------------------------------------------- > > Key: DROOLS-5125 > URL: https://issues.redhat.com/browse/DROOLS-5125 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Daniel José dos Santos > Priority: Critical > Labels: drools-tools > > In dmn diagram, each nodes has its data type. The issue affects all nodes, after reordering custom defined data types. After such reordering data types of diagram nodes are lost. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13192) Unable to remotely resolve transitives in BOM Builder

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13192?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-13192: ----------------------------------- Description: The feature introduced by WFLY-13138 is unable to remotely resolve artifacts. (was: The feature introduced by ) > Unable to remotely resolve transitives in BOM Builder > ----------------------------------------------------- > > Key: WFLY-13192 > URL: https://issues.redhat.com/browse/WFLY-13192 > Project: WildFly > Issue Type: Bug > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The feature introduced by WFLY-13138 is unable to remotely resolve artifacts. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13192) Unable to remotely resolve transitives in BOM Builder

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13192: -------------------------------------- Summary: Unable to remotely resolve transitives in BOM Builder Key: WFLY-13192 URL: https://issues.redhat.com/browse/WFLY-13192 Project: WildFly Issue Type: Bug Components: BOM Reporter: Eduardo Martins Assignee: Eduardo Martins -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13192) Unable to remotely resolve transitives in BOM Builder

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-13192?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-13192: ----------------------------------- Description: The feature introduced by > Unable to remotely resolve transitives in BOM Builder > ----------------------------------------------------- > > Key: WFLY-13192 > URL: https://issues.redhat.com/browse/WFLY-13192 > Project: WildFly > Issue Type: Bug > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The feature introduced by -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2451) FD_ALL3: improvements over FD_ALL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2451?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2451: -------------------------------- [~dan.berindei]This sound like a good solution, but I guess you meant timeout=60s in your example, didn't you? > FD_ALL3: improvements over FD_ALL > --------------------------------- > > Key: JGRP-2451 > URL: https://issues.redhat.com/browse/JGRP-2451 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.1 > > > Improvements to {{FD_ALL}}. > * Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be *default*, and as such, deprecated/removed). > * When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat > It is crucial that setting the in the map is quick, especially since this is done on every message. This should not be an issue, as we fetch the current time from the time service, which does *not* call {{System.nanoTime()}} or {{System.currentTimeMillis()}} every time. > The advantage is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P. > We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0. > However, this is only feasible with sending a message N-1 times (e.g. TCP); for UDP we don't have such an 'anycast' available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2458) Drop OSGi

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2458?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2458. ---------------------------- Resolution: Done > Drop OSGi > --------- > > Key: JGRP-2458 > URL: https://issues.redhat.com/browse/JGRP-2458 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > https://issues.redhat.com/browse/ISPN-11419 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2458) Drop OSGi

by Bela Ban (Jira)

Bela Ban created JGRP-2458: ------------------------------ Summary: Drop OSGi Key: JGRP-2458 URL: https://issues.redhat.com/browse/JGRP-2458 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 https://issues.redhat.com/browse/ISPN-11419 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13191) Docs: invalid CLI instructions in SSL and mod_cluster section

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13191?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFLY-13191: --------------------------------------- s/trust-managers/trust-manager is the fix. > Docs: invalid CLI instructions in SSL and mod_cluster section > ------------------------------------------------------------- > > Key: WFLY-13191 > URL: https://issues.redhat.com/browse/WFLY-13191 > Project: WildFly > Issue Type: Task > Components: Documentation, mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > [standalone@embedded /] /subsystem=elytron/trust-managers=default-trust-manager:write-attribute(name=certificate-revocation-list) > Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "elytron"), > ("trust-managers" => "default-trust-manager") > ]" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13191) Docs: invalid CLI instructions in SSL and mod_cluster section

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13191?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13191: ---------------------------------- Summary: Docs: invalid CLI instructions in SSL and mod_cluster section (was: Docs: invalid CLI instruction in SSL and mod_cluster section) > Docs: invalid CLI instructions in SSL and mod_cluster section > ------------------------------------------------------------- > > Key: WFLY-13191 > URL: https://issues.redhat.com/browse/WFLY-13191 > Project: WildFly > Issue Type: Task > Components: Documentation, mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > [standalone@embedded /] /subsystem=elytron/trust-managers=default-trust-manager:write-attribute(name=certificate-revocation-list) > Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [ > ("subsystem" => "elytron"), > ("trust-managers" => "default-trust-manager") > ]" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 March 2020