[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2425:
--------------------------------
Description:
This issue was spotted during DROOLS-2392 review.
In special cases undo of delete relation column is not proper.
h2. Acceptance test
# Steps to reproduce fixed (/)
# Deletion is undone properly
## Deletion of con. entry (/)
## Deletion of Dec. table row (/)
## Deletion of Dec. table column (x) DROOLS-2644
## Deletion of Relation column
## Deletion of Relation row
## Deletion of Function parameter
# Clear of expression type is undone properly
was:
This issue was spotted during DROOLS-2392 review.
In special cases undo of delete relation column is not proper.
h2. Acceptance test
# Steps to reproduce fixed (/)
# Deletion is undone properly
## Deletion of con. entry (/)
## Deletion of Dec. table row (/)
## Deletion of Dec. table column (x)
## Deletion of Relation column
## Deletion of Relation row
## Deletion of Function parameter
# Clear of expression type is undone properly
> [DMN Designer] Undo of relation column deletion is not proper
> -------------------------------------------------------------
>
> Key: DROOLS-2425
> URL: https://issues.jboss.org/browse/DROOLS-2425
> 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-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png
>
>
> This issue was spotted during DROOLS-2392 review.
> In special cases undo of delete relation column is not proper.
> h2. Acceptance test
> # Steps to reproduce fixed (/)
> # Deletion is undone properly
> ## Deletion of con. entry (/)
> ## Deletion of Dec. table row (/)
> ## Deletion of Dec. table column (x) DROOLS-2644
> ## Deletion of Relation column
> ## Deletion of Relation row
> ## Deletion of Function parameter
> # Clear of expression type is undone properly
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the decision table column causes description column width increase
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2644:
--------------------------------
Steps to Reproduce:
# Open expression editor
# Define top level as decision table
# Add one input column
# Delete one input column
## Notice width of the description column was increased
# Undo deletion of the column
## Notice deleted column was returned, however the width of the description column was not decreased to original size
The same can be seen for output column
> [DMN Designer] Deletion of the decision table column causes description column width increase
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2644
> URL: https://issues.jboss.org/browse/DROOLS-2644
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> If the user deletes * input / output column* of a decision table, then the width of the *description* column is increased to preserve total width of decision table. The problem is that when deletion of column is undone, the width of the *description* column is not returned to the original size. This issue causes unexpected context grid width increase during each *undone deletion of decision table input / output column*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the decision table column causes description column width increase
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2644:
--------------------------------
Priority: Minor (was: Major)
> [DMN Designer] Deletion of the decision table column causes description column width increase
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2644
> URL: https://issues.jboss.org/browse/DROOLS-2644
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
>
> If the user deletes * input / output column* of a decision table, then the width of the *description* column is increased to preserve total width of decision table. The problem is that when deletion of column is undone, the width of the *description* column is not returned to the original size. This issue causes unexpected context grid width increase during each *undone deletion of decision table input / output column*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the decision table column causes description column width increase
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2644:
--------------------------------
Tester: Jozef Marko
> [DMN Designer] Deletion of the decision table column causes description column width increase
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2644
> URL: https://issues.jboss.org/browse/DROOLS-2644
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> If the user deletes * input / output column* of a decision table, then the width of the *description* column is increased to preserve total width of decision table. The problem is that when deletion of column is undone, the width of the *description* column is not returned to the original size. This issue causes unexpected context grid width increase during each *undone deletion of decision table input / output column*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2644) [DMN Designer] Deletion of the decision table column causes description column width increase
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2644?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2644:
--------------------------------
Description: If the user deletes * input / output column* of a decision table, then the width of the *description* column is increased to preserve total width of decision table. The problem is that when deletion of column is undone, the width of the *description* column is not returned to the original size. This issue causes unexpected context grid width increase during each *undone deletion of decision table input / output column*
> [DMN Designer] Deletion of the decision table column causes description column width increase
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-2644
> URL: https://issues.jboss.org/browse/DROOLS-2644
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
>
> If the user deletes * input / output column* of a decision table, then the width of the *description* column is increased to preserve total width of decision table. The problem is that when deletion of column is undone, the width of the *description* column is not returned to the original size. This issue causes unexpected context grid width increase during each *undone deletion of decision table input / output column*
--
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/21/18 12:53 AM:
---------------------------------------------------------------------
-What is puzzling is that if you enable passivation after remove of remote, everything is fine.-
Thus, dialing back to minor, since workaround exist.-
was (Author: baranowb):
-What is puzzling is that if you enable passivation after remove of remote, everything is fine.
Thus, dialing back to minor, since workaround exist.-
> 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
> 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