[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN decision table
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
- Adding column
- Removing column
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
- Adding column
- Removing column
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: dtable-500-rows.dmn
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN decision table
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
> - Adding column
> - Removing column
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view (/)
- Pinned mode (/)
- Change column width, save and reopen (/)
- Search the table (/)
- Scroll the table (/)
- Edit the cell (/)
- Reorder columns (/)
- Reorder rows (/)
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
- Reorder rows
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: dtable-500-rows.dmn
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view (/)
> - Pinned mode (/)
> - Change column width, save and reopen (/)
> - Search the table (/)
> - Scroll the table (/)
> - Edit the cell (/)
> - Reorder columns (/)
> - Reorder rows (/)
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-268) Specifying empty list of headers causes fatal error
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFWIP-268?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFWIP-268:
-----------------------------------
Description:
Specifying empty list of headers causes fatal error.
{code:java}
17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: "WFLYCTL0155: 'headers' may not be null"
17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
{code}
was:
Specifying empty list of constant-headers causes fatal error.
{code:java}
17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: "WFLYCTL0155: 'headers' may not be null"
17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
{code}
> Specifying empty list of headers causes fatal error
> ---------------------------------------------------
>
> Key: WFWIP-268
> URL: https://issues.jboss.org/browse/WFWIP-268
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Specifying empty list of headers causes fatal error.
> {code:java}
> 17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: "WFLYCTL0155: 'headers' may not be null"
> 17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFWIP-268) Specifying empty list of headers causes fatal error
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFWIP-268?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFWIP-268:
-----------------------------------
Summary: Specifying empty list of headers causes fatal error (was: Specifying empty list of constant-headers causes fatal error)
> Specifying empty list of headers causes fatal error
> ---------------------------------------------------
>
> Key: WFWIP-268
> URL: https://issues.jboss.org/browse/WFWIP-268
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Tomas Terem
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: management
>
> Specifying empty list of constant-headers causes fatal error.
> {code:java}
> 17:15:30,603 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("management-interface" => "http-interface")
> ]) - failure description: "WFLYCTL0155: 'headers' may not be null"
> 17:15:30,604 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 17:15:30,614 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 11.0.0.Beta3-SNAPSHOT stopped in 6ms
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-4735:
----------------------------------------
[~jomarko] Decision Table with 500 rows attached.
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: dtable-500-rows.dmn
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> - Reorder columns
> - Reorder rows
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-4735:
-----------------------------------
Attachment: dtable-500-rows.dmn
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Attachments: dtable-500-rows.dmn
>
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> - Reorder columns
> - Reorder rows
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (WFLY-12806) Upgrade to Wildfly 17, can't find persistence unit
by Emilio Cuberos (Jira)
[ https://issues.jboss.org/browse/WFLY-12806?page=com.atlassian.jira.plugin... ]
Emilio Cuberos updated WFLY-12806:
----------------------------------
Description:
Hi,
Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17.
Now the persistence units (attached persistence.xml) are no longer found:
{code:java}
Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}}
{code}
Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml:
{code:java}
package com.hemocue.cloud.repository;
import com.hemocue.cloud.entity.user.Program;
import javax.enterprise.context.Dependent;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
/**
*
* @author Ivar Grimstad (ivar.grimstad(a)gmail.com)
*/
@Dependent
public class ProgramRepository extends AbstractRepository<Program> {
@PersistenceContext(unitName = "healthtrender-core")
private EntityManager em;
@Override
EntityManager entityManager() {
return em;
}
}
{code}
was:
Hi,
Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17.
Now the persistence units (attached persistence.xml) are no longer found:
{code:java}
Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}}
{code}
Here is an example of class where we inject a persistence-unit. In this example it's called "healthtrender-core" which is present in the persistence.xml:
{code:java}
package com.hemocue.cloud.repository;
import com.hemocue.cloud.entity.user.Program;
import javax.enterprise.context.Dependent;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
/**
*
* @author Ivar Grimstad (ivar.grimstad(a)gmail.com)
*/
@Dependent
public class ProgramRepository extends AbstractRepository<Program> {
@PersistenceContext(unitName = "healthtrender-core")
private EntityManager em;
@Override
EntityManager entityManager() {
return em;
}
}
{code}
> Upgrade to Wildfly 17, can't find persistence unit
> --------------------------------------------------
>
> Key: WFLY-12806
> URL: https://issues.jboss.org/browse/WFLY-12806
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Emilio Cuberos
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: persistence.xml
>
>
> Hi,
> Could you give us some advice? We upgraded from Java 8 / Wildfly 10, to Java 11 and Wildfly 17.
> Now the persistence units (attached persistence.xml) are no longer found:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: WFLYWELD0037: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named 'healthtrender-core' in deployment healthtrender-cloud-1.0.0.war for injection point private javax.persistence.EntityManager com.hemocue.cloud.repository.UserProfileRepository.em"}}
> {code}
> Here is an example of class where we inject a persistence-unit called "healthtrender-core" which is present in the persistence.xml:
> {code:java}
> package com.hemocue.cloud.repository;
> import com.hemocue.cloud.entity.user.Program;
> import javax.enterprise.context.Dependent;
> import javax.persistence.EntityManager;
> import javax.persistence.PersistenceContext;
> /**
> *
> * @author Ivar Grimstad (ivar.grimstad(a)gmail.com)
> */
> @Dependent
> public class ProgramRepository extends AbstractRepository<Program> {
> @PersistenceContext(unitName = "healthtrender-core")
> private EntityManager em;
> @Override
> EntityManager entityManager() {
> return em;
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months
[JBoss JIRA] (DROOLS-4735) [DMN Designer] Grid performance is dire
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4735?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4735:
--------------------------------
Description:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
- Reorder rows
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
was:
There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
On closer inspection the following issues were found:
- Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
- Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
h2. Manual Acceptance test
h3. GDT
- Merge view
- Pinned mode
- Change column width, save and reopen
- Search the table
- Scroll the table
- Edit the cell
- Reorder columns
- Reorder rows(? not sure this is possible with GDT)
h3. DMN
- Context ( Context (Decision Table, Relation, Invocation))
- Change column width, save and reopen
- Search the grid
- Scroll the grid
- Reorder columns
- Reorder rows
> [DMN Designer] Grid performance is dire
> ---------------------------------------
>
> Key: DROOLS-4735
> URL: https://issues.jboss.org/browse/DROOLS-4735
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.29.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> There have been reports that the performance of the DMN editor's grids does not scale. On examination performance for anything other than simple examples is pretty dire.. something is seriously wrong.
> On closer inspection the following issues were found:
> - Multiple {{NodeMouseDownHandler}}, {{NodeMouseMoveHandler}} and {{NodeMouseUpHandler}} are registered because multiple {{DMNGridLayer}} are (incorrectly) instantiated due to a flaw in {{GridLienzoPanel}} and {{GridLienzoScrollHandler}}.
> - Calls to {{GridWidget.getHeight()}} and {{GridRow.getHeight()}} can be _very_ expensive for due to the dynamic calculation in {{ExpressionEditorGridRow}} and {{LiteralExpressionGridRow}} rows.
> h2. Manual Acceptance test
> h3. GDT
> - Merge view
> - Pinned mode
> - Change column width, save and reopen
> - Search the table
> - Scroll the table
> - Edit the cell
> - Reorder columns
> - Reorder rows
> h3. DMN
> - Context ( Context (Decision Table, Relation, Invocation))
> - Change column width, save and reopen
> - Search the grid
> - Scroll the grid
> - Reorder columns
> - Reorder rows
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 8 months