[JBoss JIRA] (DROOLS-2640) [DMN Designer] First function language definitions
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2640:
-----------------------------------
Summary: [DMN Designer] First function language definitions
Key: DROOLS-2640
URL: https://issues.jboss.org/browse/DROOLS-2640
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.8.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-06-18 09-54-07.png, Screenshot from 2018-06-18 09-54-15.png
This was spotted during review of DROOLS-2454 however not sure if it is related. The problem occurs if you declare the function language for the first time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3934) CLI output compact response option
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-3934:
--------------------------------------------
Summary: CLI output compact response option
Key: WFCORE-3934
URL: https://issues.jboss.org/browse/WFCORE-3934
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 4.0.0.Final
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
The response outputs with new lines in an easy to read format, it would also be useful to output in a compact form as users will use --output-json and echo-dmr to get the output needed to post via http to the management interface.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2473) [DMN Designer] Function language change inconsistency
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2473?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2473:
--------------------------------
Summary: [DMN Designer] Function language change inconsistency (was: [DMN Designer] Function language change)
> [DMN Designer] Function language change inconsistency
> -----------------------------------------------------
>
> Key: DROOLS-2473
> URL: https://issues.jboss.org/browse/DROOLS-2473
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-04-13 09-13-54.png, Screenshot from 2018-04-13 09-14-00.png, Screenshot from 2018-04-13 09-14-14.png
>
>
> If the function language is changed, the boxed expression table is not rendered as expected.
> h2. PR Acceptance Test
> Change of function language is consistent in rendering
> - Empty function
> - Function with data
> - Function as boxed expression not at top level in the context hierarchy
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10280) Can't enable stateful EJB passivation when EJB remote service is removed
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-10280?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski edited comment on WFLY-10280 at 6/18/18 3:50 AM:
--------------------------------------------------------------------
Current error:
10:05:54,328 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,329 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "async-operations")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,329 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "expiration")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "listener")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "persistence")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "remote-command")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "state-transfer")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,331 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "transport")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,331 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("transport" => "none")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
WFLYCTL0184: New missing/unsatisfied dependencies:
service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (missing) dependents: [service org.wildfly.clustering.cache.registry.ejb.client-mappings]
was (Author: baranowb):
Current error:
10:05:54,328 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,329 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "async-operations")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,329 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "expiration")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "listener")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "persistence")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "remote-command")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,330 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "state-transfer")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,331 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("thread-pool" => "transport")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
10:05:54,331 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "ejb"),
("transport" => "none")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.clustering.cache.registry-entry.ejb.client-mappings"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.clustering.cache.registry.ejb.client-mappings is missing [org.wildfly.clustering.cache.registry-entry.ejb.client-mappings]"]
}
> Can't enable stateful EJB passivation when EJB remote service is removed
> ------------------------------------------------------------------------
>
> Key: WFLY-10280
> URL: https://issues.jboss.org/browse/WFLY-10280
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 12.0.0.Final
> Reporter: Ladislav Thon
> Assignee: Bartosz Baranowski
> Priority: Minor
> Attachments: tinyEjbPassivation.war
>
>
> In WildFly Swarm, we don't have EJB remoting enabled by default, but would still like to be able to use stateful EJB passivation. We can't because of this bug.
> What I do here is change the default SFSB cache to {{passivating}}, thereby enabling SFSB passivation, and also remove the {{remote}} service (which is what we do in WildFly Swarm by default).
> When reloading the server to normal mode, deployment fails with a lot of errors, the main culprit seems to be the EJB client mappings registry:
> {code}
> 17:16:37,216 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."tinyEjbPassivation.war".HelloBean.bean-manager (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.cache]
> service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.START (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."tinyEjbPassivation.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./tinyEjbPassivation, service jboss.deployment.unit."tinyEjbPassivation.war".WeldEndInitService]
> service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.cache (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".component.HelloBean.START]
> service jboss.undertow.deployment.default-server.default-host./tinyEjbPassivation (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".deploymentCompleteService]
> service org.wildfly.clustering.cache.registry.ejb.client-mappings (unavailable) dependents: [service jboss.deployment.unit."tinyEjbPassivation.war".HelloBean.bean-manager]
> service org.wildfly.clustering.cache.registry-entry.ejb.client-mappings (missing) dependents: [service org.wildfly.clustering.cache.registry.ejb.client-mappings]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2454:
--------------------------------
Description:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen (/)
# Define top level as Function, add a lot of parameters, reopen (/)
# Define top level as Context, recursively add more Contexts, reopen (/)
was:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen (/)
# Define top level as Function, add a lot of parameters, reopen (/)
# Define top level as Context, recursively add more Contexts, reopen
> [DMN Designer] Decision content not visible after reopen
> --------------------------------------------------------
>
> Key: DROOLS-2454
> URL: https://issues.jboss.org/browse/DROOLS-2454
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png
>
>
> If the decision with bigger context table is reopened, its content is not visible.
> h2. PR Manual Acceptance test
> In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
> # Steps to reproduce fixed (/)
> # Define top level as Literal expression, reopen (/)
> # Define top level as Decision table, add columns, reopen (/)
> # Define top level as Relation, add columns, reopen (/)
> # Define top level as Invocation, specify complex parameters, reopen (/)
> # Define top level as Function, add a lot of parameters, reopen (/)
> # Define top level as Context, recursively add more Contexts, reopen (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2454:
--------------------------------
Description:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen (/)
# Define top level as Function, add a lot of parameters, reopen (/)
# Define top level as Context, recursively add more Contexts, reopen
was:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen (/)
# Define top level as Function, add a lot of parameters, reopen
# Define top level as Context, recursively add more Contexts, reopen
> [DMN Designer] Decision content not visible after reopen
> --------------------------------------------------------
>
> Key: DROOLS-2454
> URL: https://issues.jboss.org/browse/DROOLS-2454
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png
>
>
> If the decision with bigger context table is reopened, its content is not visible.
> h2. PR Manual Acceptance test
> In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
> # Steps to reproduce fixed (/)
> # Define top level as Literal expression, reopen (/)
> # Define top level as Decision table, add columns, reopen (/)
> # Define top level as Relation, add columns, reopen (/)
> # Define top level as Invocation, specify complex parameters, reopen (/)
> # Define top level as Function, add a lot of parameters, reopen (/)
> # Define top level as Context, recursively add more Contexts, reopen
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2454:
--------------------------------
Description:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen (/)
# Define top level as Function, add a lot of parameters, reopen
# Define top level as Context, recursively add more Contexts, reopen
was:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen
# Define top level as Function, add a lot of parameters, reopen
# Define top level as Context, recursively add more Contexts, reopen
> [DMN Designer] Decision content not visible after reopen
> --------------------------------------------------------
>
> Key: DROOLS-2454
> URL: https://issues.jboss.org/browse/DROOLS-2454
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png
>
>
> If the decision with bigger context table is reopened, its content is not visible.
> h2. PR Manual Acceptance test
> In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
> # Steps to reproduce fixed (/)
> # Define top level as Literal expression, reopen (/)
> # Define top level as Decision table, add columns, reopen (/)
> # Define top level as Relation, add columns, reopen (/)
> # Define top level as Invocation, specify complex parameters, reopen (/)
> # Define top level as Function, add a lot of parameters, reopen
> # Define top level as Context, recursively add more Contexts, reopen
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2454:
--------------------------------
Description:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen (/)
# Define top level as Invocation, specify complex parameters, reopen
# Define top level as Function, add a lot of parameters, reopen
# Define top level as Context, recursively add more Contexts, reopen
was:
If the decision with bigger context table is reopened, its content is not visible.
h2. PR Manual Acceptance test
In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
# Steps to reproduce fixed (/)
# Define top level as Literal expression, reopen (/)
# Define top level as Decision table, add columns, reopen (/)
# Define top level as Relation, add columns, reopen
# Define top level as Invocation, specify complex parameters, reopen
# Define top level as Function, add a lot of parameters, reopen
# Define top level as Context, recursively add more Contexts, reopen
> [DMN Designer] Decision content not visible after reopen
> --------------------------------------------------------
>
> Key: DROOLS-2454
> URL: https://issues.jboss.org/browse/DROOLS-2454
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png
>
>
> If the decision with bigger context table is reopened, its content is not visible.
> h2. PR Manual Acceptance test
> In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
> # Steps to reproduce fixed (/)
> # Define top level as Literal expression, reopen (/)
> # Define top level as Decision table, add columns, reopen (/)
> # Define top level as Relation, add columns, reopen (/)
> # Define top level as Invocation, specify complex parameters, reopen
> # Define top level as Function, add a lot of parameters, reopen
> # Define top level as Context, recursively add more Contexts, reopen
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month