[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3095:
----------------------------------
Description:
As user I want to use multiple instances of my DO in a test scenario.
*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The workflow to define template creation is going to change because of the new header level: now user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
was:
As user I want to use multiple instances of my DO in a scenario.
*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> As user I want to use multiple instances of my DO in a test scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The workflow to define template creation is going to change because of the new header level: now user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3133) Add support for EXPECTED conditions on new object
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3133?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3133:
----------------------------------
Component/s: Scenario Simulation and Testing
> Add support for EXPECTED conditions on new object
> -------------------------------------------------
>
> Key: DROOLS-3133
> URL: https://issues.jboss.org/browse/DROOLS-3133
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
>
> As user I want to define in the EXPECTED section conditions on instances that are generated during rule execution and not only on object defined in the GIVEN section.
> In other words I want to define I expect that during rule execution it will be generated an instance of a specific type and that satisfy some conditions
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-2788:
---------------------------------
Tester: Klara Kufova (was: Juraj Soltes)
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3133) Add support for EXPECTED conditions on new object
by Daniele Zonca (Jira)
Daniele Zonca created DROOLS-3133:
-------------------------------------
Summary: Add support for EXPECTED conditions on new object
Key: DROOLS-3133
URL: https://issues.jboss.org/browse/DROOLS-3133
Project: Drools
Issue Type: Story
Reporter: Daniele Zonca
Assignee: Daniele Zonca
As user I want to define in the EXPECTED section conditions on instances that are generated during rule execution and not only on object defined in the GIVEN section.
In other words I want to define I expect that during rule execution it will be generated an instance of a specific type and that satisfy some conditions
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Daniele Zonca resolved DROOLS-2788.
-----------------------------------
Resolution: Done
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2788:
---------------------------------------
Ok we created this item to track current development activities and we will update use it to write implementation specs about what we are doing.
https://issues.jboss.org/browse/DROOLS-3095
I am going to close this item
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png, one.png, two.png, zero.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3095:
----------------------------------
Description:
As user I want to use multiple instances of my DO in a scenario.
*Implementation specs:*
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
was:
Implement "Instance" concept on the GIVEN/EXPECTED columns.
Given/Expected columns should have three headers:
# the top one is the group (GIVEN/EXPECTED),
# the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
# the third one is the specific property of the instance.
Below every instance header there could be one ore more property header - each of them belonging to that instance.
The user must define the type/name of the instance *before* mapping the final properties.
When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
These issue is related to https://issues.jboss.org/browse/DROOLS-2788
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> As user I want to use multiple instances of my DO in a scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3095) Grid with multiple data/domain object instances
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3095?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3095:
----------------------------------
Issue Type: Story (was: Task)
> Grid with multiple data/domain object instances
> -----------------------------------------------
>
> Key: DROOLS-3095
> URL: https://issues.jboss.org/browse/DROOLS-3095
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
>
> As user I want to use multiple instances of my DO in a scenario.
> *Implementation specs:*
> Implement "Instance" concept on the GIVEN/EXPECTED columns.
> Given/Expected columns should have three headers:
> # the top one is the group (GIVEN/EXPECTED),
> # the second one is the actual instance of a given type (ex Person1, Person2, Dispute)
> # the third one is the specific property of the instance.
> Below every instance header there could be one ore more property header - each of them belonging to that instance.
> The user must define the type/name of the instance *before* mapping the final properties.
> When clicking on a GIVEN "Instance" header, user should see only first-level data objects in the right panel.
> When clicking on a Property header, user should see only first-level properties of the Instance it belongs to.
> When When clicking on an EXPECT "Instance" header, user should see only first-level data objects in the right panel *AND* the GIVEN instances.
> Changing Instance type is not allowed (dose not makes sense): only "DELETE" is possible at "Instance" level. Deleting an Instance header(column) recursively delete all the properties.
> These issue is related to https://issues.jboss.org/browse/DROOLS-2788
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11165) Eliminate unessential module dependencies on the org.jboss.as.transactions module
by Ondra Chaloupka (Jira)
[ https://issues.jboss.org/browse/WFLY-11165?page=com.atlassian.jira.plugin... ]
Ondra Chaloupka commented on WFLY-11165:
----------------------------------------
hi [~bstansberry], I currently investigate on splitting the transaction module dependencies. I was thinking to split the transaction dependency jar dependency (tracked at https://issues.jboss.org/browse/WFLY-9588). I just experiment with the approach and I haven't discussed it in the Narayana team yet. So maybe it will be a wrong way.
Anyway I can be of help with this issue in scope of the Galleon task (even I can assign this task to me). I have to admit I lack a bit the expertise in Galleon to cover the context so I would need some clues, possibly.
> Eliminate unessential module dependencies on the org.jboss.as.transactions module
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11165
> URL: https://issues.jboss.org/browse/WFLY-11165
> Project: WildFly
> Issue Type: Enhancement
> Components: Class Loading, Management, Transactions
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> As part of our work on getting maximum benefit from Galleon, we want to eliminate unnecessary hard dependencies between Galleon packages, most of which are just provisioning wrappers around the FS content for our JBoss Modules modules. So that means cutting dependency links between modules.
> The org.jboss.as.transactions module necessarily has a large dependency tree, so if other modules depend on it, they then also have a large dependency tree, perhaps much larger than whatever they really need. So I want to eliminate such dependencies whereever possible.
> There are quite a few modules that depend on org.jboss.as.transactions solely for ServiceName constants for services that provide value types not from org.jboss.as.transactions, e.g. TransactionManager which is from the javax.transaction.api module. So the main (perhaps only) task here will be to eliminate those links.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3037) [DMN Designer] Added item definition has not icon of structure
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3037?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-3037.
-------------------------------
Resolution: Cannot Reproduce
Works fine on master.
> [DMN Designer] Added item definition has not icon of structure
> --------------------------------------------------------------
>
> Key: DROOLS-3037
> URL: https://issues.jboss.org/browse/DROOLS-3037
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-09-26 12-33-28.png, initial-prototypes.png
>
>
> If user add custom item definition and define it as structure, the item definition misses the structure icon set the attached picture. There is new custom structure item definition *a* without icon. Compare it with other structure item definitions.
> h2. Acceptance test
> - Check added item definition has icon when it is top level
> - Check added item definition has icon when used in nested level
> - Check item definition has not structure icon when changed from structure to something else
> - Check item definition has structure icon when changed from something else to structure
> - Check item definition has structure icon if item definition is recursive
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months