[JBoss JIRA] (JGRP-2495) A variant of RELAY2.printTopology() returning a member list
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2495?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2495.
----------------------------
Resolution: Won't Fix
> A variant of RELAY2.printTopology() returning a member list
> -----------------------------------------------------------
>
> Key: JGRP-2495
> URL: https://issues.redhat.com/browse/JGRP-2495
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 4.0.24
> Reporter: S Pokutniy
> Assignee: Bela Ban
> Priority: Minor
>
> It would be great if there existed a variant of A variant of RELAY2.printTopology() function, returning a list of all members with their logical names and physical addresses. As of now printTopology(boolean) returns a string with all members. Even though the members of one site do not know about the members of the other site, it would still be great to be able to show the list of all members connected over the bridge, be it for demonstration or monitoring purpose.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5235) An existing decision table already binding an object doesn't see when a field is added to that object
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5235?page=com.atlassian.jira.plug... ]
Toni Rikkola reassigned DROOLS-5235:
------------------------------------
Assignee: Toni Rikkola (was: Michael Anstis)
> An existing decision table already binding an object doesn't see when a field is added to that object
> -----------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5235
> URL: https://issues.redhat.com/browse/DROOLS-5235
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Reporter: Mario Fusco
> Assignee: Toni Rikkola
> Priority: Major
>
> Steps to reproduce:
> 1. Create a data object with a few fields
> 2. Create a Guided decision table with at least a condition column binding that object
> 3. Go back to the object definition and add a new field and save
> 4. Go back to the decision table and add a second column condition on the same object: the newly added field is not available among the other old fields in the drop down menu
> Note that if you create a brand new table and try to add a condition on that object than also the new field is available.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-5090) enumeration values used in rules can be deleted
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5090?page=com.atlassian.jira.plug... ]
Toni Rikkola reassigned DROOLS-5090:
------------------------------------
Assignee: Toni Rikkola (was: Michael Anstis)
> enumeration values used in rules can be deleted
> -----------------------------------------------
>
> Key: DROOLS-5090
> URL: https://issues.redhat.com/browse/DROOLS-5090
> Project: Drools
> Issue Type: Bug
> Components: Enumerations Editor
> Reporter: Werner Van Herrewegen
> Assignee: Toni Rikkola
> Priority: Major
>
> As a rule creator,
> whenever the value list of an enumeration gets modified, I want to make sure that no rules are broken because of it.
> NOW IT IS BROKEN:
> see steps to reproduce
> solution suggestion:
> prevent the deletion of an enumeration value when it is in use in a rule
> The user should be made aware what rule(s) is/are blocking the removal of a value!
> --> the user must first 'prepare' the rules and then come back to remove the value from the list
> ATTENTION:
> This logic only is valid for DELETION/RENAMING of enumeration values,
> Rearranging values and adding values can happen without any problem.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months