[JBoss JIRA] (DROOLS-3113) [DMN Designer] Data Types - Edit mode inconsistency
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3113?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3113:
---------------------------------------
Description:
*Prerequisite:*
- Existing custom item definitions in the model
*Step to reproduce:*
- Open manage custom data type dialog
- Click edit to entry 1
- Insert above from entry 2
- Notice entry 1 will stay in edit mode
- Insert above from entry 1
- Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
Expected scenario:
- We should keep edit mode active regardless of the creation type.
Source: https://issues.jboss.org/browse/DROOLS-3024?focusedCommentId=13645851&pag...
was:
*Prerequisite:*
- existing custom item definitions in model
*Step to reproduce:*
- Open manage custom data type dialog
- Click edit to entry 1
- Insert above from entry 2
- Notice entry 1 will stay in edit mode
- Insert above from entry 1
- Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
> [DMN Designer] Data Types - Edit mode inconsistency
> ---------------------------------------------------
>
> Key: DROOLS-3113
> URL: https://issues.jboss.org/browse/DROOLS-3113
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
>
> *Prerequisite:*
> - Existing custom item definitions in the model
> *Step to reproduce:*
> - Open manage custom data type dialog
> - Click edit to entry 1
> - Insert above from entry 2
> - Notice entry 1 will stay in edit mode
> - Insert above from entry 1
> - Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
> Expected scenario:
> - We should keep edit mode active regardless of the creation type.
> Source: https://issues.jboss.org/browse/DROOLS-3024?focusedCommentId=13645851&pag...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3113) [DMN Designer] Data Types - Edit mode inconsistency
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3113?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3113:
---------------------------------------
Description:
*Prerequisite:*
- Existing custom item definitions in the model
*Step to reproduce:*
- Open manage custom data type dialog
- Click edit to entry 1
- Insert above from entry 2
- Notice entry 1 will stay in edit mode
- Insert above from entry 1
- Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
*Expected scenario:*
- We should keep edit mode active regardless of the creation type.
Source: https://issues.jboss.org/browse/DROOLS-3024?focusedCommentId=13645851&pag...
was:
*Prerequisite:*
- Existing custom item definitions in the model
*Step to reproduce:*
- Open manage custom data type dialog
- Click edit to entry 1
- Insert above from entry 2
- Notice entry 1 will stay in edit mode
- Insert above from entry 1
- Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
Expected scenario:
- We should keep edit mode active regardless of the creation type.
Source: https://issues.jboss.org/browse/DROOLS-3024?focusedCommentId=13645851&pag...
> [DMN Designer] Data Types - Edit mode inconsistency
> ---------------------------------------------------
>
> Key: DROOLS-3113
> URL: https://issues.jboss.org/browse/DROOLS-3113
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
>
> *Prerequisite:*
> - Existing custom item definitions in the model
> *Step to reproduce:*
> - Open manage custom data type dialog
> - Click edit to entry 1
> - Insert above from entry 2
> - Notice entry 1 will stay in edit mode
> - Insert above from entry 1
> - Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
> *Expected scenario:*
> - We should keep edit mode active regardless of the creation type.
> Source: https://issues.jboss.org/browse/DROOLS-3024?focusedCommentId=13645851&pag...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3113) [DMN Designer] Data Types - Edit mode inconsistency
by Guilherme Carreiro (Jira)
Guilherme Carreiro created DROOLS-3113:
------------------------------------------
Summary: [DMN Designer] Data Types - Edit mode inconsistency
Key: DROOLS-3113
URL: https://issues.jboss.org/browse/DROOLS-3113
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Guilherme Carreiro
Assignee: Guilherme Carreiro
*Prerequisite:*
- existing custom item definitions in model
*Step to reproduce:*
- Open manage custom data type dialog
- Click edit to entry 1
- Insert above from entry 2
- Notice entry 1 will stay in edit mode
- Insert above from entry 1
- Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3113) [DMN Designer] Data Types - Edit mode inconsistency
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3113?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-3113:
---------------------------------------
Priority: Minor (was: Major)
> [DMN Designer] Data Types - Edit mode inconsistency
> ---------------------------------------------------
>
> Key: DROOLS-3113
> URL: https://issues.jboss.org/browse/DROOLS-3113
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Minor
> Labels: drools-tools
>
> *Prerequisite:*
> - existing custom item definitions in model
> *Step to reproduce:*
> - Open manage custom data type dialog
> - Click edit to entry 1
> - Insert above from entry 2
> - Notice entry 1 will stay in edit mode
> - Insert above from entry 1
> - Notice the edit mode of entry 1 will be canceled and changes done in name will be saved, changes in data type will be lost
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on WFLY-5550:
------------------------------------
[~tommaso-borgato] Re: jboss-web.xml options:
The link you pasted is documentation from a very old JBoss AS 4.2.2.
* replication-trigger has dropped from version 8.0 of the jboss-web.xml schema and has been ignored since EAP 7.0, following the redesign/reimplementation of the distributed session manager
* FIELD granularity was dropped since EAP5.
* replication-field-batch-mode is specific to FIELD granularity, and was has also dropped in EAP5.
Re: missing options from jboss-web.xml
I do not intend to add any new options to jboss-web.xml. In fact, the entire <replication-config/> is being dropped from the jboss-web.xml schema. Configuration of the distributed session manager will no longer be done via this deployment descriptor, unless a legacy application is deployed (i.e. containing an old version of jboss-web.xml).
> Formalize web session clustering modules into a proper subsystem
> ----------------------------------------------------------------
>
> Key: WFLY-5550
> URL: https://issues.jboss.org/browse/WFLY-5550
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.CR3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Major
>
> Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.
> Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
> This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name). jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3056) [DMN Designer] Data Types - List View Performance - The view items take ~100ms to be instantiated
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3056?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3056:
--------------------------------
Description:
The creation of a new {{DataTypeListItem}} [here|https://github.com/kiegroup/kie-wb-common/blob/7f9a51f866fca11f7e7b1...] takes 100ms. This impacts the load time of the Data Types dialog when the user has many data types (e.g. more than 100).
To solve this problem, we can pre-instantiate a poll of views and re-use them or take new views from this pool. I just validate this idea with a PoC, and I could reduce 70% of the load time.
h2. Acceptance test
# A lot of custom items, add top level item
# A lot of custom items, remove top level item
# Nested levels, add new deepest level item
# Nested levels, remove deepest level item
was:
The creation of a new {{DataTypeListItem}} [here|https://github.com/kiegroup/kie-wb-common/blob/7f9a51f866fca11f7e7b1...] takes 100ms. This impacts the load time of the Data Types dialog when the user has many data types (e.g. more than 100).
To solve this problem, we can pre-instantiate a poll of views and re-use them or take new views from this pool. I just validate this idea with a PoC, and I could reduce 70% of the load time.
> [DMN Designer] Data Types - List View Performance - The view items take ~100ms to be instantiated
> -------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3056
> URL: https://issues.jboss.org/browse/DROOLS-3056
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Major
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn
>
>
> The creation of a new {{DataTypeListItem}} [here|https://github.com/kiegroup/kie-wb-common/blob/7f9a51f866fca11f7e7b1...] takes 100ms. This impacts the load time of the Data Types dialog when the user has many data types (e.g. more than 100).
> To solve this problem, we can pre-instantiate a poll of views and re-use them or take new views from this pool. I just validate this idea with a PoC, and I could reduce 70% of the load time.
> h2. Acceptance test
> # A lot of custom items, add top level item
> # A lot of custom items, remove top level item
> # Nested levels, add new deepest level item
> # Nested levels, remove deepest level item
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months