[JBoss JIRA] (DROOLS-3759) Extends editing support inside CollectionEditor
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3759?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3759:
---------------------------------
Attachment: (was: dmn-map.dmn)
> Extends editing support inside CollectionEditor
> -----------------------------------------------
>
> Key: DROOLS-3759
> URL: https://issues.jboss.org/browse/DROOLS-3759
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: 1.png
>
>
> Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
> It should be possible to *at least* insert/edit first-level complex properties
> h3. Issues that need to be addressed as a part of this task:
> # The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
> !1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3765) Enable the pod to act as a comsumer or producer
by Massimiliano Dessi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3765?page=com.atlassian.jira.plugi... ]
Massimiliano Dessi commented on DROOLS-3765:
--------------------------------------------
The pods use a configmap to elect the leader, an update is sent to all the pods in the cluster the behaviour is the following:
The leader consume the user topic and in the handle event it produce a event on the master topic, the slaves consumes the events in the master topic.
If the leader is lost a new leader is elected and the slave turned into new leader change is topic to consume in 10 seconds.
> Enable the pod to act as a comsumer or producer
> ------------------------------------------------
>
> Key: DROOLS-3765
> URL: https://issues.jboss.org/browse/DROOLS-3765
> Project: Drools
> Issue Type: Sub-task
> Reporter: Massimiliano Dessi
> Assignee: Massimiliano Dessi
> Priority: Major
>
> The pod must act as a consumer or producer using the status of Master (consumer and producer) or slave (consumer)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3759) Extends editing support inside CollectionEditor
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3759?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3759:
-------------------------------------
Description:
Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
It should be possible to *at least* insert/edit first-level complex properties
h3. Issues that need to be addressed as a part of this task:
# The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
!1.png|thumbnail!
was:
Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
It should be possible to *at least* insert/edit first-level complex properties
h3. Issues that need to be addressed as a part of this task:
# The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
!1.png|thumbnail!
# Moving a column from the EXPECT to the GIVEN section of the table and invoking the collection popup causes the following unexpected error:
{{Uncaught exception: Index: 0, Size: 0}}
Try this DMN file: [^dmn-map.dmn] (and move {{database}} from EXPECT to GIVEN).
Summary: Extends editing support inside CollectionEditor (was: Allowing nested property editing inside CollectionEditor)
> Extends editing support inside CollectionEditor
> -----------------------------------------------
>
> Key: DROOLS-3759
> URL: https://issues.jboss.org/browse/DROOLS-3759
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: 1.png, dmn-map.dmn
>
>
> Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
> It should be possible to *at least* insert/edit first-level complex properties
> h3. Issues that need to be addressed as a part of this task:
> # The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
> !1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3759) Allowing nested property editing inside CollectionEditor
by Klara Kufova (Jira)
[ https://issues.jboss.org/browse/DROOLS-3759?page=com.atlassian.jira.plugi... ]
Klara Kufova updated DROOLS-3759:
---------------------------------
Description:
Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
It should be possible to *at least* insert/edit first-level complex properties
h3. Issues that need to be addressed as a part of this task:
# The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
!1.png|thumbnail!
# Moving a column from the EXPECT to the GIVEN section of the table and invoking the collection popup causes the following unexpected error:
{{Uncaught exception: Index: 0, Size: 0}}
Try this DMN file: [^dmn-map.dmn] (and move {{database}} from EXPECT to GIVEN).
was:
Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
It should be possible to *at least* insert/edit first-level complex properties
> Allowing nested property editing inside CollectionEditor
> --------------------------------------------------------
>
> Key: DROOLS-3759
> URL: https://issues.jboss.org/browse/DROOLS-3759
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: 1.png, dmn-map.dmn
>
>
> Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean).
> It should be possible to *at least* insert/edit first-level complex properties
> h3. Issues that need to be addressed as a part of this task:
> # The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed:
> !1.png|thumbnail!
> # Moving a column from the EXPECT to the GIVEN section of the table and invoking the collection popup causes the following unexpected error:
> {{Uncaught exception: Index: 0, Size: 0}}
> Try this DMN file: [^dmn-map.dmn] (and move {{database}} from EXPECT to GIVEN).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3767) Reset "isEditing" status flag inside gridcell
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-3767?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-3767:
-------------------------------
Sprint: 2019 Week 11-13
> Reset "isEditing" status flag inside gridcell
> ---------------------------------------------
>
> Key: DROOLS-3767
> URL: https://issues.jboss.org/browse/DROOLS-3767
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
>
> Our _ScenarioGridCell_ has an _isEditingMode_ flag.
> If the flag is _true_, the editing does not start.
> When starting editing a grid celll, the _isEditingMode_ flag is set to _true_.
> Normally, this flag is set back to _false_ when editing finish.
> Currently, if for some reason an exception is thrown soon after start editing, the flag remains _true_, and it is not possible to start editing the cell again (unless closing and reopening the asset).
> This should be fixed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months