[JBoss JIRA] (WFCORE-4191) Fix IO Metrics Registration
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFCORE-4191?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-4191:
--------------------------------
Description:
* shutdown-requested is a (boolean) runtime read-only attribute, not a metric
* the other attributes are correctly registered as metrics. However their definition should not specify "undefined metric value" as their values can always be computed.
was:
shutdown-requested is a (boolean) runtime read-only attribute, not a metric
> Fix IO Metrics Registration
> ---------------------------
>
> Key: WFCORE-4191
> URL: https://issues.jboss.org/browse/WFCORE-4191
> Project: WildFly Core
> Issue Type: Bug
> Components: IO
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> * shutdown-requested is a (boolean) runtime read-only attribute, not a metric
> * the other attributes are correctly registered as metrics. However their definition should not specify "undefined metric value" as their values can always be computed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3193) UX to support selection of multiple data/domain object instances
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3193:
---------------------------------------
No, the user can give labels to instances (e.g. the "seller" label for the Company instance) or to attributes (e.g., a "cs" label to a credit score attribute on a Person instance). Each row is a scenario/test, so having numbered rows make sense.
[~danielezonca] any concerns/thoughts?
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. 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-3193) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3193:
-------------------------------------
[~tirelli] Thanks, good to know - no numbering of instances. Is there any concept of column number/position (like a spreadsheet) that needs to be worked into the UI ?
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. 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-3193) UX to support selection of multiple data/domain object instances
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Edson Tirelli edited comment on DROOLS-3193 at 10/30/18 10:10 AM:
------------------------------------------------------------------
Liz, no, the labels are arbitrary. We should not "number" instances.
For instance, pretend I am creating a scenario that involves a sale of goods between two companies. I can label one company "seller" and the other company "buyer".
|| seller : Company | buyer: Company ||
|| ... | ... ||
was (Author: tirelli):
Liz, no, the labels are arbitrary. We should not "number" instances.
For instance, pretent I am creating a scenario that involves a sale of goods between two companies. I can label one company "seller" and the other company "buyer".
|| seller : Company | buyer: Company ||
|| ... | ... ||
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. 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-3193) UX to support selection of multiple data/domain object instances
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3193:
---------------------------------------
Liz, no, the labels are arbitrary. We should not "number" instances.
For instance, pretent I am creating a scenario that involves a sale of goods between two companies. I can label one company "seller" and the other company "buyer".
|| seller : Company | buyer: Company ||
|| ... | ... ||
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. 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-3193) UX to support selection of multiple data/domain object instances
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3193?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3193:
-------------------------------------
[~kkufova][~tirelli] Should data object instances be ID'd in the table by column position or instance number (2nd instance of x, or 2nd column position?)
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-3193
> URL: https://issues.jboss.org/browse/DROOLS-3193
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
>
> As user I want to use multiple instances of the same data object in my test scenarios (multiple instances support) (i.e. 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-3202) [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a built in Data Type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3202?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3202:
--------------------------------
Description:
The Data Type dialog cannot allow the following data type names:
- number
- string
- boolean
- days and time duration
- years and months duration
- time
- date and time
- any
- date
- context
A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
h2. Acceptance test
- Creation of a new data type (/)
- Editing an existing data type (/)
was:
The Data Type dialog cannot allow the following data type names:
- number
- string
- boolean
- days and time duration
- years and months duration
- time
- date and time
- any
- date
- context
A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
h2. Acceptance test
- Creation of a new (/)
- Editing an existing
> [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a built in Data Type
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-3202
> URL: https://issues.jboss.org/browse/DROOLS-3202
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> The Data Type dialog cannot allow the following data type names:
> - number
> - string
> - boolean
> - days and time duration
> - years and months duration
> - time
> - date and time
> - any
> - date
> - context
> A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
> h2. Acceptance test
> - Creation of a new data type (/)
> - Editing an existing data type (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3202) [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a built in Data Type
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3202?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3202:
--------------------------------
Description:
The Data Type dialog cannot allow the following data type names:
- number
- string
- boolean
- days and time duration
- years and months duration
- time
- date and time
- any
- date
- context
A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
h2. Acceptance test
- Creation of a new (/)
- Editing an existing
was:
The Data Type dialog cannot allow the following data type names:
- number
- string
- boolean
- days and time duration
- years and months duration
- time
- date and time
- any
- date
- context
A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
h2. Acceptance test
- Creation of a new
- Editing an existing
> [DMN Designer] Data Type dialog - Validation - Data Type name cannot be a built in Data Type
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-3202
> URL: https://issues.jboss.org/browse/DROOLS-3202
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
>
> The Data Type dialog cannot allow the following data type names:
> - number
> - string
> - boolean
> - days and time duration
> - years and months duration
> - time
> - date and time
> - any
> - date
> - context
> A validation (error) message should be shown to the user alerting that the operation mentioned above is not allowed.
> h2. Acceptance test
> - Creation of a new (/)
> - Editing an existing
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months