[JBoss JIRA] (DROOLS-3438) Cancel Scenario Simulation edit mode
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3438?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3438:
-----------------------------------
Sprint: 2019 Week 05-07, 2019 Week 08-10 (was: 2019 Week 05-07)
> Cancel Scenario Simulation edit mode
> ------------------------------------
>
> Key: DROOLS-3438
> URL: https://issues.jboss.org/browse/DROOLS-3438
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.16.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> User is able to edit grid cell by pressing an enter. Currently the edit mode is cancelled by *Shift + Tab* combination. We have to change this to:
> - *Tab* for cancel edit mode and *store* the value
> - *Esc* for cancel edit mode and *discard* the value
> This defect is caused by keyboard shortcuts implemented as part of DROOLS-2932.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3175) [DMN Designer] keyboard context menu invocation
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3175?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3175:
-----------------------------------
Sprint: 2018 Week 42-44, 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07, 2019 Week 08-10 (was: 2018 Week 42-44, 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07)
> [DMN Designer] keyboard context menu invocation
> -----------------------------------------------
>
> Key: DROOLS-3175
> URL: https://issues.jboss.org/browse/DROOLS-3175
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-01-30 15-04-02.png
>
>
> User should be able to invoke context menu by keyboard. Context menu contains actions according to the cell, where it was invoked. Possibility to invoke the context menu is crucial for integration selenium tests.
> h2. TODO
> - DMN - undefined cell (/)
> - DMN - After selection of menu item the focus is lost
> - Scenario - proper menu for description column (/)
> - Scenario - enable menu even when not bound (/)
> - Tests (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3425) Unexpected behavior of docks when multiple editors are opened
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3425?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3425:
-----------------------------------
Sprint: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07, 2019 Week 08-10 (was: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07)
> Unexpected behavior of docks when multiple editors are opened
> -------------------------------------------------------------
>
> Key: DROOLS-3425
> URL: https://issues.jboss.org/browse/DROOLS-3425
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor, Scenario Simulation and Testing, Stunner
> Reporter: Klara Kufova
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: ScenarioSimulation, drools-tools
> Attachments: screencast-11-12-18.webm, screencast-12-12-18.webm
>
>
> When multiple assets are opened in different editors, their docks incorrectly interfere. After opening two assets in a row, the Business Central freezes with an unexpected error. Closing one asset causes unexpected disappearance of the left panel.
> See the attached screencast for detailed information. After the assets are opened for the first time, everything seems correct. Once the {{.dmn}} file is opened for the second time, the issues start to occur.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11716) Deployment Fails with @Transactional in Passivating Scope Bean
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/WFLY-11716?page=com.atlassian.jira.plugin... ]
Tom Jenkinson reassigned WFLY-11716:
------------------------------------
Assignee: Matej Novotny (was: Tom Jenkinson)
> Deployment Fails with @Transactional in Passivating Scope Bean
> --------------------------------------------------------------
>
> Key: WFLY-11716
> URL: https://issues.jboss.org/browse/WFLY-11716
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Transactions
> Affects Versions: 16.0.0.Beta1
> Environment: Java 8, Ubuntu Xenial
> Reporter: Cody Lerum
> Assignee: Matej Novotny
> Priority: Major
> Attachments: jsf-npe.zip
>
>
> On Wildfly 16.0.0.Beta1 deployment fails
> {code}
> org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001477: The bean Managed Bean [class co.cfly.oss.lerg.rateCenter.inventoryRequest.InventoryRequestView] with qualifiers [@Default @Any @Named] declares a passivating scope but has a(n) Interceptor [class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired intercepts @Transactional] with a non-passivation-capable dependency com.arjuna.ats.jta.cdi.JNDIBean@12e2cb9f
> at org.jboss.weld.bootstrap.Validator.validateInterceptorDecoratorInjectionPointPassivationCapable(Validator.java:480)
> at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:225)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
> at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months