[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2911:
---------------------------------------
[~manstis] [~roger.martinez] [~mark.proctor] FYI
This is the list of activities to move current interfaces to common module.
Most of the activities are not directly related to interface update but to some needed refactors and some steps to enable simple undo strategy
> Update Scenario Simulation command to use the new module
> --------------------------------------------------------
>
> Key: DROOLS-2911
> URL: https://issues.jboss.org/browse/DROOLS-2911
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Use new kie-wb-common-command-api for Scenario Simulation commands
> *Specs:*
> Preliminary steps:
> * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
> * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
> * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
> Move to common API:
> * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
> * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
> * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
> * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
> * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-2911:
----------------------------------
Description:
Use new kie-wb-common-command-api for Scenario Simulation commands
*Specs:*
Preliminary steps:
* Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
* Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
* Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
Move to common API:
* Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
* Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
* Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
* Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
* Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
was:
Use new kie-wb-common-command-api for Scenario Simulation commands
*Specs:*
Preliminary steps:
* Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
* Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
* Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
Move to common API:
* Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
* Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
* Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
* Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
* Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
> Update Scenario Simulation command to use the new module
> --------------------------------------------------------
>
> Key: DROOLS-2911
> URL: https://issues.jboss.org/browse/DROOLS-2911
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> Use new kie-wb-common-command-api for Scenario Simulation commands
> *Specs:*
> Preliminary steps:
> * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
> * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
> * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
> Move to common API:
> * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
> * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
> * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
> * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
> * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ]
Daniele Zonca reassigned DROOLS-2911:
-------------------------------------
Assignee: Gabriele Cardosi (was: Daniele Zonca)
> Update Scenario Simulation command to use the new module
> --------------------------------------------------------
>
> Key: DROOLS-2911
> URL: https://issues.jboss.org/browse/DROOLS-2911
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Use new kie-wb-common-command-api for Scenario Simulation commands
> *Specs:*
> Preliminary steps:
> * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
> * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
> * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
> Move to common API:
> * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
> * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
> * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
> * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
> * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-2911:
----------------------------------
Sprint: 2018 Week 45-47
> Update Scenario Simulation command to use the new module
> --------------------------------------------------------
>
> Key: DROOLS-2911
> URL: https://issues.jboss.org/browse/DROOLS-2911
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
>
> Use new kie-wb-common-command-api for Scenario Simulation commands
> *Specs:*
> Preliminary steps:
> * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
> * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
> * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
> Move to common API:
> * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
> * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
> * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
> * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
> * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-2911) Update Scenario Simulation command to use the new module
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2911?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-2911:
----------------------------------
Description:
Use new kie-wb-common-command-api for Scenario Simulation commands
*Specs:*
Preliminary steps:
* Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
* Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
* Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
Move to common API:
* Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
* Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
* Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
* Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
* Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
was:Use new kie-wb-common-command-api for Scenario Simulation commands
> Update Scenario Simulation command to use the new module
> --------------------------------------------------------
>
> Key: DROOLS-2911
> URL: https://issues.jboss.org/browse/DROOLS-2911
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> Use new kie-wb-common-command-api for Scenario Simulation commands
> *Specs:*
> Preliminary steps:
> * Split CommandExecutor class into two classes: a pure executor and a general event handler that accepts all the events
> * Refactor ScenarioGridMode.bindContent and ScenarioSimulationViewImpl.refreshContent to be able to refresh internal model and grid model in a simple way (for now it refreshes only the errors from the internal model)
> * Refactor remaining actions with no commands (for instance flush of inline editing should fire an event instead of update directly the code). More or less all the methods that work with ScenarioGridModel should be inside a command
> Move to common API:
> * Implement ScenarioCommandManager extending org.kie.workbench.common.command.impl.CommandManagerImpl
> * Refactor all commands to extend org.kie.workbench.common.command.AbstractCommand
> * Implement a default undo strategy that dump the model and restore it when needed (we should consider how to *preserve selections, columns width and right panel status*)
> * Implement ScenarioCommandRegistry extending org.kie.workbench.common.command.registry.command.CommandRegistryImpl
> * Implement ScenarioCommandController (or with a better name :) ) that wrap ScenarioCommandRegistry and ScenarioCommandManager and exposes some API for safe command execute (for instance undo only of the last executed method). This class should be the entry point to manage commands (probably it should be declared as @Dependent and injected into the Presenter)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list
by Ron Murhammer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ]
Ron Murhammer edited comment on DROOLS-3098 at 11/13/18 1:07 PM:
-----------------------------------------------------------------
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts (GIVEN data)
- hasMultipleContacts (rules will set this field)
- hasDuplicatePhoneNumbers (rules will set this field)
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron (has list of phone numbers)
-- Home 111-111-1111
-- Cell 222-222-2222
- Liz (has list of phone numbers)
-- Home 333-333-3333
-- Cell 444-444-4444
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
was (Author: ron-murhammer):
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron (has list of phone numbers)
-- Home 111-111-1111
-- Cell 222-222-2222
- Liz (has list of phone numbers)
-- Home 333-333-3333
-- Cell 444-444-4444
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
> UX: Add support for map and list
> --------------------------------
>
> Key: DROOLS-3098
> URL: https://issues.jboss.org/browse/DROOLS-3098
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to be able to use Data Objects that contain Lists and Maps
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list
by Ron Murhammer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ]
Ron Murhammer edited comment on DROOLS-3098 at 11/13/18 1:01 PM:
-----------------------------------------------------------------
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron (has list of phone numbers)
-- Home 111-111-1111
-- Cell 222-222-2222
- Liz (has list of phone numbers)
-- Home 333-333-3333
-- Cell 444-444-4444
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
was (Author: ron-murhammer):
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron
- Liz (has list of phone numbers)
-- Home 111-111-1111
-- Cell 222-222-222
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
> UX: Add support for map and list
> --------------------------------
>
> Key: DROOLS-3098
> URL: https://issues.jboss.org/browse/DROOLS-3098
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to be able to use Data Objects that contain Lists and Maps
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11328) EE Concurency Utilities "hung-task-threshold" / "long-running-tasks" do not work and are not implemented as explained
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11328?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-11328:
----------------------------------------
I don't really like the idea of aborting threads and after digging in EE Concurrency RI I found that checking a thread status wrt this threshold param locks the thread, so I don't really like the idea of using its functionality in short periods either. I see two resolutions for this JIRA:
a) Forget about the RI functionality, i.e. remove the related configuration params and update docs
b) Implement a non intrusive periodic check (at least 1 minute) that just logs if threads are considered hung, and/or a management op that does the same on demand
One thing I also discovered is that hung task threshold param is delegated to the thread factory used by the executor, which means that if an executor shares a factory, the default config that plugs the default managed thread factory in the executor, the last executor created overrides older ones configs.
> EE Concurency Utilities "hung-task-threshold" / "long-running-tasks" do not work and are not implemented as explained
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11328
> URL: https://issues.jboss.org/browse/WFLY-11328
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Major
>
> ee subsystem parameters "hung-task-threshold" and "long-running-tasks" for managed-executor-service / managed-scheduled-executor-service do not work and are not implemented as described in [EAP 7 Development Guide|https://access.redhat.com/documentation/en-us/red_hat_jboss_enterpr...]:
> - hung-task-threshold: Defines the time, in milliseconds, after which tasks are considered hung by the managed executor service and forcefully aborted. If the value is 0 (which is the default), tasks are never considered hung.
> - long-running-tasks: Suggests optimizing the execution of long running tasks, and defaults to false.
> I tested with [EAP 7 QuickStarts managed-executor-service example|https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.0...] but these paremeters doe not take any effect:
> - tasks exceeding hung-task-threshold are never forcefully aborted. And there's no way to detect hung tasks exceeding hung-task-threshold.
> - setting long-running-tasks to true does not change the behavior.
> As far as I checked the source code, I noticed the following:
> - EAP 7.x uses the EE Concurency Utilities RI [org.glassfish.enterprise.concurrent|https://github.com/javaee/cu-ri] internally and just passes the paramters to the RI.
> - In the EE Concurency Utilities RI, these parameters are used in the methods [ManagedThreadFactoryImpl#isTaskHung(long now)|https://github.com/javaee/cu-ri/blob/master/src/main/java/org/glassf...], [AbstractManagedExecutorService#getHungThreads()|https://github.com/javaee...] and [AbstractManagedExecutorService#isLongRunningTasks()|https://github.com/ja...] (AbstractManagedExecutorService is the parent class of ManagedExecutorServiceImpl / ManagedScheduledExecutorServiceImpl).
> - However, these methods are never invoked from EAP 7.x. So, these parameters do not take any effect in EAP 7.x.
> - In addition, even if these methods are used, it looks the implementation is totally different from the description in the documentation. The parameter "long-running-tasks" is just used as a flag to skip from checking hung thread detection. And the parameter "hung-task-threshold" never forcefully abort the hung thread exceeding the threshold.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list
by Ron Murhammer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ]
Ron Murhammer edited comment on DROOLS-3098 at 11/13/18 12:44 PM:
------------------------------------------------------------------
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron
- Liz (has list of phone numbers)
-- Home 111-111-1111
-- Cell 222-222-222
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
was (Author: ron-murhammer):
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron
- Liz (has list of phone numbers)
--- Home 111-111-1111
--- Cell 222-222-222
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
> UX: Add support for map and list
> --------------------------------
>
> Key: DROOLS-3098
> URL: https://issues.jboss.org/browse/DROOLS-3098
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to be able to use Data Objects that contain Lists and Maps
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3098) UX: Add support for map and list
by Ron Murhammer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ]
Ron Murhammer commented on DROOLS-3098:
---------------------------------------
More explanation of Daniele's example:
I have a ContactList which has a List of Contacts. Each Contact has a list of Phone Numbers. Each Phone Number has a couple of field like the actual number and the type (home, work, cell, etc).
*ContactList Fields*
- List of Contacts
- hasMultipleContacts
- hasDuplicatePhoneNumbers
*Example Data:*
ContactList (has list of contacts)
- Daniele
- Ron
- Liz (has list of phone numbers)
--- Home 111-111-1111
--- Cell 222-222-222
*Test Cases*
1. I want to create the above data in the given section UI table and have a rule that checks that I have multiple contacts in the contact list. Then in expect check that ContactList.hasMultipleContacts == true.
2. I want to create the above data in the given section UI table and have a rule that checks that across contacts, there aren't any duplicate phone numbers. Then in the expect check that ContactList.hasDuplicatePhoneNumbers == false.
> UX: Add support for map and list
> --------------------------------
>
> Key: DROOLS-3098
> URL: https://issues.jboss.org/browse/DROOLS-3098
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to be able to use Data Objects that contain Lists and Maps
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months