[JBoss JIRA] (WFLY-10117) HTTP + EJB - UnsupportedOperationException trying to write to an AbstractMap
by Tomas Remes (JIRA)
Tomas Remes created WFLY-10117:
----------------------------------
Summary: HTTP + EJB - UnsupportedOperationException trying to write to an AbstractMap
Key: WFLY-10117
URL: https://issues.jboss.org/browse/WFLY-10117
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Tomas Remes
Assignee: Stuart Douglas
Fix For: 13.0.0.Beta1
[~tremes] Has hit this failure when running some tests against our OpenShift images using WF code from, I believe, 12 CR1.
{code}
13:03:50,832 ERROR [org.jboss.as.ejb3.remote] (default task-1) WFLYEJB0150: Could not write method invocation failure for method public abstract void com.redhat.xpaas.ejb.server.RemoteCounter.increment() on bean named CounterBean for appname modulename ROOT distinctname due to: java.lang.UnsupportedOperationException
at java.util.AbstractMap.put(AbstractMap.java:209)
at org.jboss.as.ejb3.remote.AssociationImpl.updateAffinities(AssociationImpl.java:267)
at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:233)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
{code}
He or [~luck3y] can give you more details re the specific test.
Just walking through code, my guess is the Collections.emptyMap() produced at [1] is getting passed through the stack to the failing code. (I'm filing this because I did this bit of brilliant analysis. ;) )
[1] https://github.com/wildfly/wildfly-http-client/blob/master/ejb/src/main/j...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10115) Regression in JMS bridge with network failures tests
by Martin Styk (JIRA)
Martin Styk created WFLY-10115:
----------------------------------
Summary: Regression in JMS bridge with network failures tests
Key: WFLY-10115
URL: https://issues.jboss.org/browse/WFLY-10115
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Martin Styk
Assignee: Jeff Mesnil
Priority: Blocker
Attachments: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip
*Scenario*
Node A and B are started. JMS bridge with {{once and only once}} delivery and 1 reconnect attempt is deployed on node A. Producer starts sending mix of normal and large messages to InQueue on node A. Jms bridge resends messages from A's InQueue to B's OutQueue. During this time short network failure sequence (network goes down and then up) is executed twice. Receiver receives messages from OutQueue(also from node A). After that, network stays disconnected. Another receiver receives remaining messages from A's InQueue.
{noformat:title=Jms Bridge}
<jms-bridge name="myBridge" module="org.apache.activemq.artemis" quality-of-service="ONCE_AND_ONLY_ONCE" failure-retry-interval="1000" max-retries="1" max-batch-size="10" max-batch-time="100" add-messageID-in-header="true">
<source connection-factory="java:/ConnectionFactory" destination="jms/queue/InQueue"/>
<target connection-factory="jms/BridgeConnectionFactory" destination="jms/queue/OutQueue">
<target-context>
<property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/>
<property name="java.naming.provider.url" value="http-remoting://127.0.0.1:9080"/>
</target-context>
</target>
</jms-bridge>
{noformat}
*Issue*
* node A's InQueue and node B's OutQueue is empty
* There are no prepared transactions on node A
* some messages *are missing* after test (multiply of 10, which is number of messages in one transaction)
* this scenario fails *intermittently*
Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
Logs are attached.
--
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
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
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
> 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
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10115) Regression in JMS bridge with network failures tests
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFLY-10115?page=com.atlassian.jira.plugin... ]
Martin Styk updated WFLY-10115:
-------------------------------
Attachment: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip
> Regression in JMS bridge with network failures tests
> ----------------------------------------------------
>
> Key: WFLY-10115
> URL: https://issues.jboss.org/browse/WFLY-10115
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
> Priority: Blocker
> Attachments: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip
>
>
> *Scenario*
> Node A and B are started. JMS bridge with {{once and only once}} delivery and 1 reconnect attempt is deployed on node A. Producer starts sending mix of normal and large messages to InQueue on node A. Jms bridge resends messages from A's InQueue to B's OutQueue. During this time short network failure sequence (network goes down and then up) is executed twice. Receiver receives messages from OutQueue(also from node A). After that, network stays disconnected. Another receiver receives remaining messages from A's InQueue.
> {noformat:title=Jms Bridge}
> <jms-bridge name="myBridge" module="org.apache.activemq.artemis" quality-of-service="ONCE_AND_ONLY_ONCE" failure-retry-interval="1000" max-retries="1" max-batch-size="10" max-batch-time="100" add-messageID-in-header="true">
> <source connection-factory="java:/ConnectionFactory" destination="jms/queue/InQueue"/>
> <target connection-factory="jms/BridgeConnectionFactory" destination="jms/queue/OutQueue">
> <target-context>
> <property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/>
> <property name="java.naming.provider.url" value="http-remoting://127.0.0.1:9080"/>
> </target-context>
> </target>
> </jms-bridge>
> {noformat}
> *Issue*
> * node A's InQueue and node B's OutQueue is empty
> * There are no prepared transactions on node A
> * some messages *are missing* after test (multiply of 10, which is number of messages in one transaction)
> * this scenario fails *intermittently*
> Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
> Logs are attached.
--
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
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
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
> 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
--
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
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
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)
## See PR comment No. 2
# 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
> 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
--
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)
## See PR comment No. 2
# 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
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
# 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)
> ## See PR comment No. 2
> # 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
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month