[JBoss JIRA] (WFLY-10119) Add multi-server support to mod_cluster
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-10119:
-------------------------------------
Summary: Add multi-server support to mod_cluster
Key: WFLY-10119
URL: https://issues.jboss.org/browse/WFLY-10119
Project: WildFly
Issue Type: Feature Request
Components: mod_cluster
Affects Versions: 10.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-6803:
---------------------------------
Description: Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server. (was: Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778).
mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server.)
> Add multi-server support to mod_cluster
> ---------------------------------------
>
> Key: WFLY-6803
> URL: https://issues.jboss.org/browse/WFLY-6803
> Project: WildFly
> Issue Type: Enhancement
> Components: mod_cluster
> Affects Versions: 10.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
>
> Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
## DROOLS-2435
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons (/)
> ## expression types distinguished
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
> # check situation when multiple nodes has the same name, empty name (/)
> ## same names no problem, empty name replace with node type, nice
> # Check case when DRG contains a lot of nodes , if possible to view all of them (/)
> ## scrollbar appears, and disappear according to count of nodes, nice
> # Check case when some decision has a lot of inputs - all of them visible (?)
> ## not checked, because not able to connect DRG nodes
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - does not prevent from merge
> # Check if navigator dock can be resized (/)
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name (/)
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node (/)
> ## opened DRG, clicked DRD (x)
> ### DROOLS-2432 does not prevent from merge
> ## opened DRD, clicked other DRD (/)
> ## opened DRD, clicked DRG node (/)
> # Check behavior if user tries to select multiple entries in navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to invoke context menu from navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to drag some elements in navigator (/)
> ## not implemented, but fine, no exception
> h3. Sorting
> # nodes sorted asc, changes in node names reflected in order (/)
> # rename some DRG nodes, check navigator keeps selected sorting (/)
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo (x)
> ## DROOLS-2433
> # rename some DRG nodes, undo redo, check changes reflected in navigator (/)
> # delete DRG node, undo redo, check changes reflected in navigator (/)
> # clear DRD node, undo redo, check changes reflected in navigator (x)
> ## DROOLS-2434
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator (/)
> # clear DRD node, check changes reflected in navigator (x)
> ## DROOLS-2434
> # Drag DRG elements, no effect to expected (/)
> # Rebuild connections, change should appear in navigator (?)
> ## not checked, because not able to connect DRG nodes
> # Check multiple connections, input node connected to multiple decisions ... (?)
> ## not checked, because not able to connect DRG nodes
> # Long node names (/) perfect
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving (x)
> ## DROOLS-2435
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected (/)
# Rebuild connections, change should appear in navigator (?)
## not checked, because not able to connect DRG nodes
# Check multiple connections, input node connected to multiple decisions ... (?)
## not checked, because not able to connect DRG nodes
# Long node names (/) perfect
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons (/)
> ## expression types distinguished
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
> # check situation when multiple nodes has the same name, empty name (/)
> ## same names no problem, empty name replace with node type, nice
> # Check case when DRG contains a lot of nodes , if possible to view all of them (/)
> ## scrollbar appears, and disappear according to count of nodes, nice
> # Check case when some decision has a lot of inputs - all of them visible (?)
> ## not checked, because not able to connect DRG nodes
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - does not prevent from merge
> # Check if navigator dock can be resized (/)
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name (/)
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node (/)
> ## opened DRG, clicked DRD (x)
> ### DROOLS-2432 does not prevent from merge
> ## opened DRD, clicked other DRD (/)
> ## opened DRD, clicked DRG node (/)
> # Check behavior if user tries to select multiple entries in navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to invoke context menu from navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to drag some elements in navigator (/)
> ## not implemented, but fine, no exception
> h3. Sorting
> # nodes sorted asc, changes in node names reflected in order (/)
> # rename some DRG nodes, check navigator keeps selected sorting (/)
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo (x)
> ## DROOLS-2433
> # rename some DRG nodes, undo redo, check changes reflected in navigator (/)
> # delete DRG node, undo redo, check changes reflected in navigator (/)
> # clear DRD node, undo redo, check changes reflected in navigator (x)
> ## DROOLS-2434
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator (/)
> # clear DRD node, check changes reflected in navigator (x)
> ## DROOLS-2434
> # Drag DRG elements, no effect to expected (/)
> # Rebuild connections, change should appear in navigator (?)
> ## not checked, because not able to connect DRG nodes
> # Check multiple connections, input node connected to multiple decisions ... (?)
> ## not checked, because not able to connect DRG nodes
> # Long node names (/) perfect
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2349) [DMN Editor] Decision Navigator dock
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2349?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2349:
--------------------------------
Description:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator (x)
## DROOLS-2434
h3. Synchronization
# delete DRG node, check changes reflected in navigator (/)
# clear DRD node, check changes reflected in navigator (x)
## DROOLS-2434
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
was:
The "Decision Navigator" is docked next to the Project Explorer. See:
!prototype.png|thumbnail!
- Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
- User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
- Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
- The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
h2. Acceptance tests
h3. Prerequisite
Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
# Check node icons (/)
## expression types distinguished
h3. Expand / Collapse
# check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
# check situation when multiple nodes has the same name, empty name (/)
## same names no problem, empty name replace with node type, nice
# Check case when DRG contains a lot of nodes , if possible to view all of them (/)
## scrollbar appears, and disappear according to count of nodes, nice
# Check case when some decision has a lot of inputs - all of them visible (?)
## not checked, because not able to connect DRG nodes
h3. Full screen mode
# check behavior of navigator when DMN designer is used in full screen mode (x)
## DROOLS-2431 - does not prevent from merge
# Check if navigator dock can be resized (/)
h3. Navigation
# check *back to* link present if DRD opened and shows proper node name (/)
# check click in Navigator dock cause either selecting DRG node or opening given DRD
## opened DRG, clicked other DRG node (/)
## opened DRG, clicked DRD (x)
### DROOLS-2432 does not prevent from merge
## opened DRD, clicked other DRD (/)
## opened DRD, clicked DRG node (/)
# Check behavior if user tries to select multiple entries in navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to invoke context menu from navigator (/)
## not implemented, but fine, no exception
# Check behavior if user tries to drag some elements in navigator (/)
## not implemented, but fine, no exception
h3. Sorting
# nodes sorted asc, changes in node names reflected in order (/)
# rename some DRG nodes, check navigator keeps selected sorting (/)
h3. Undo / Redo
# change selection in navigator, check behavior of undo redo (x)
## DROOLS-2433
# rename some DRG nodes, undo redo, check changes reflected in navigator (/)
# delete DRG node, undo redo, check changes reflected in navigator (/)
# clear DRD node, undo redo, check changes reflected in navigator
h3. Synchronization
# delete DRG node, check changes reflected in navigator
# clear DRD node, check changes reflected in navigator
# Drag DRG elements, no effect to expected
# Rebuild connections, change should appear in navigator
# Check multiple connections, input node connected to multiple decisions ...
# Long node names
# Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
> [DMN Editor] Decision Navigator dock
> ------------------------------------
>
> Key: DROOLS-2349
> URL: https://issues.jboss.org/browse/DROOLS-2349
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Attachments: prototype.png
>
>
> The "Decision Navigator" is docked next to the Project Explorer. See:
> !prototype.png|thumbnail!
> - Tree navigation offers a view of the entire DRG. Diagram nodes are represented within the tree.
> - User defined DRD’s are represented as top level tree nodes, with supporting decision and input data represented as subordinate tree nodes.
> - Tree structure only goes as deep as primary logic definition, such as a decision table (nested logic is not represented in the tree.)
> - The Navigator includes a preview image which represents a thumbnail view of the diagram view selected.
> h2. Acceptance tests
> h3. Prerequisite
> Prepare non empty DRD diagram, specify expressions in decisions, ensure DRG contains all node types
> # Check node icons (/)
> ## expression types distinguished
> h3. Expand / Collapse
> # check that expand / collapse shows always all elements, doesn't change order between expanding/collapsing (/)
> # check situation when multiple nodes has the same name, empty name (/)
> ## same names no problem, empty name replace with node type, nice
> # Check case when DRG contains a lot of nodes , if possible to view all of them (/)
> ## scrollbar appears, and disappear according to count of nodes, nice
> # Check case when some decision has a lot of inputs - all of them visible (?)
> ## not checked, because not able to connect DRG nodes
> h3. Full screen mode
> # check behavior of navigator when DMN designer is used in full screen mode (x)
> ## DROOLS-2431 - does not prevent from merge
> # Check if navigator dock can be resized (/)
> h3. Navigation
> # check *back to* link present if DRD opened and shows proper node name (/)
> # check click in Navigator dock cause either selecting DRG node or opening given DRD
> ## opened DRG, clicked other DRG node (/)
> ## opened DRG, clicked DRD (x)
> ### DROOLS-2432 does not prevent from merge
> ## opened DRD, clicked other DRD (/)
> ## opened DRD, clicked DRG node (/)
> # Check behavior if user tries to select multiple entries in navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to invoke context menu from navigator (/)
> ## not implemented, but fine, no exception
> # Check behavior if user tries to drag some elements in navigator (/)
> ## not implemented, but fine, no exception
> h3. Sorting
> # nodes sorted asc, changes in node names reflected in order (/)
> # rename some DRG nodes, check navigator keeps selected sorting (/)
> h3. Undo / Redo
> # change selection in navigator, check behavior of undo redo (x)
> ## DROOLS-2433
> # rename some DRG nodes, undo redo, check changes reflected in navigator (/)
> # delete DRG node, undo redo, check changes reflected in navigator (/)
> # clear DRD node, undo redo, check changes reflected in navigator (x)
> ## DROOLS-2434
> h3. Synchronization
> # delete DRG node, check changes reflected in navigator (/)
> # clear DRD node, check changes reflected in navigator (x)
> ## DROOLS-2434
> # Drag DRG elements, no effect to expected
> # Rebuild connections, change should appear in navigator
> # Check multiple connections, input node connected to multiple decisions ...
> # Long node names
> # Changes in DRD, navigate to other DRG node, other DRD, then return to first DRD, check changes present without saving
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2434) [DMN Designer] Navigator reaction on clear command
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2434?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2434:
--------------------------------
Summary: [DMN Designer] Navigator reaction on clear command (was: [DMN Designer])
> [DMN Designer] Navigator reaction on clear command
> --------------------------------------------------
>
> Key: DROOLS-2434
> URL: https://issues.jboss.org/browse/DROOLS-2434
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
> Attachments: Screenshot from 2018-03-28 10-10-16.png, Screenshot from 2018-03-28 10-10-27.png, Screenshot from 2018-03-28 10-10-34.png, Screenshot from 2018-03-28 10-10-42.png
>
>
> Clear of expression in DRD is not reflected in navigator. See steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2434) [DMN Designer]
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2434:
-----------------------------------
Summary: [DMN Designer]
Key: DROOLS-2434
URL: https://issues.jboss.org/browse/DROOLS-2434
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Jozef Marko
Assignee: Guilherme Carreiro
Priority: Minor
Attachments: Screenshot from 2018-03-28 10-10-16.png, Screenshot from 2018-03-28 10-10-27.png, Screenshot from 2018-03-28 10-10-34.png, Screenshot from 2018-03-28 10-10-42.png
Clear of expression in DRD is not reflected in navigator. See steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month