[JBoss JIRA] (DROOLS-4026) Quick test tool useful during DMN authoring
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4026?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-4026:
-------------------------------------
[~dmarrazzo] Thank you, I understand what you miss now. However I still think we should reuse scenarios for this. For example my idea: Provide values just of given columns, click run, and show actual values. Next to it facilitate switching between scenario and dmn.
> Quick test tool useful during DMN authoring
> -------------------------------------------
>
> Key: DROOLS-4026
> URL: https://issues.jboss.org/browse/DROOLS-4026
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Donato Marrazzo
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, drools-tools
>
> As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test.
> When the user run the test he can get back the results of the DMN execution.
> Moreover, it would be handy to add those input/output to an existing (or new) test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-4027) Test Scenario: improve the DMN asset selection experience
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4027?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-4027:
------------------------------------------
[~manstis]
Hi. This issue is included inside https://issues.jboss.org/browse/DROOLS-3420 (that has a broader scope).
Moreover, I've already replaced (in my submarine branch) the combobox with the KieAssetDropdown.
> Test Scenario: improve the DMN asset selection experience
> ---------------------------------------------------------
>
> Key: DROOLS-4027
> URL: https://issues.jboss.org/browse/DROOLS-4027
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Environment: Create a new Test Scenario for DMN
> Reporter: Donato Marrazzo
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: Field, drools-tools
> Attachments: Screenshot from 2019-05-15 06-35-52.png
>
>
> When a user creates a new Test Scenario for DMN, he has to choose the DMN asset:
> !Screenshot from 2019-05-15 06-35-52.png!
> The asset is presented with the full physical path, which is a bit confusing even because it does not fit the field length.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-4026) Quick test tool useful during DMN authoring
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-4026?page=com.atlassian.jira.plugi... ]
Donato Marrazzo commented on DROOLS-4026:
-----------------------------------------
Hi [~jomarko], the main point here is to have a probing tool during the authoring phase:
1. It should be on the side and let the user inspect the DMN model, i.e. the user understands from the model that there is a threshold of 1000, so s/he can probe with a value above or under the threshold.
2. Majority of the probes are just a quick experiment in the "try and error" cycle, so I don't expect the user want to create always a test scenario.
3. While DMN designer builds the model, s/he needs to check the correctness of a partial model, maybe later when the model will be complete those probing values will be useless or inconsistent.
The main downsides of the test scenarios for this purpose are:
1. you cannot see at sametime the DMN model
2. you have to put the expected output, whereas you just want to inject inputs and see the results
> Quick test tool useful during DMN authoring
> -------------------------------------------
>
> Key: DROOLS-4026
> URL: https://issues.jboss.org/browse/DROOLS-4026
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Reporter: Donato Marrazzo
> Assignee: Michael Anstis
> Priority: Major
> Labels: Field, drools-tools
>
> As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test.
> When the user run the test he can get back the results of the DMN execution.
> Moreover, it would be handy to add those input/output to an existing (or new) test scenario.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3990) Document keyboard shortcuts for menus in DM.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3990?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3990:
----------------------------------------
[~uxdlc] Yes, that is correct. At present the only menu-centric keyboard shortcuts are for the Data Types related kebab pop-over menu.
I say at present as, with most things, if we need more menu keyboard shortcuts open a JIRA requesting such :-)
> Document keyboard shortcuts for menus in DM.
> --------------------------------------------
>
> Key: DROOLS-3990
> URL: https://issues.jboss.org/browse/DROOLS-3990
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Jozef Marko
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: kebab-shortcuts.png
>
>
> As a business analyst practitioner, I would like to view the keyboard shortcuts in the context of the menu actions that they refer to.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3877) DMN Decision table headers: Add edit table actions to contextual menu.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3877?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3877:
-----------------------------------
Fix Version/s: 7.22.0.Final
> DMN Decision table headers: Add edit table actions to contextual menu.
> ----------------------------------------------------------------------
>
> Key: DROOLS-3877
> URL: https://issues.jboss.org/browse/DROOLS-3877
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: Field, UX, UXTeam, drools-tools
> Fix For: 7.22.0.Final
>
> Attachments: Screen Shot 2019-04-18 at 5.04.49 PM.png, Screen Shot 2019-05-02 at 10.00.20 AM.png, Screen Shot 2019-05-02 at 10.02.13 AM.png, header-context.png, header-context2b.png
>
>
> As a user of this feature I want to have the possibility to add columns or rows in a DT when right-clicking on the table header.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-4027) Test Scenario: improve the DMN asset selection experience
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4027?page=com.atlassian.jira.plugi... ]
Michael Anstis reassigned DROOLS-4027:
--------------------------------------
Assignee: Gabriele Cardosi (was: Michael Anstis)
> Test Scenario: improve the DMN asset selection experience
> ---------------------------------------------------------
>
> Key: DROOLS-4027
> URL: https://issues.jboss.org/browse/DROOLS-4027
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.21.0.Final
> Environment: Create a new Test Scenario for DMN
> Reporter: Donato Marrazzo
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: Field, drools-tools
> Attachments: Screenshot from 2019-05-15 06-35-52.png
>
>
> When a user creates a new Test Scenario for DMN, he has to choose the DMN asset:
> !Screenshot from 2019-05-15 06-35-52.png!
> The asset is presented with the full physical path, which is a bit confusing even because it does not fit the field length.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11907) NPE trying to use Resteasy Client inside CDI Async Event
by Matěj Novotný (Jira)
[ https://issues.jboss.org/browse/WFLY-11907?page=com.atlassian.jira.plugin... ]
Matěj Novotný commented on WFLY-11907:
--------------------------------------
[~clerum] Weld side of things has been fixed in WELD-2573 for quite some time. That gets into WFLY 17 under Weld 3.1.1.Final.
I left this issue open in case resteasy will want to fix something on their end (null checks for TCCL?). But that's for [~ron_sigal] to decide; if not action is to be taken, we can close this issue.
> NPE trying to use Resteasy Client inside CDI Async Event
> --------------------------------------------------------
>
> Key: WFLY-11907
> URL: https://issues.jboss.org/browse/WFLY-11907
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 14.0.0.Final, 16.0.0.Final
> Reporter: Cody Lerum
> Assignee: Matěj Novotný
> Priority: Major
>
> When attempting to use the Resteasy Client inside a CDI Async Event a NPE is thrown.
> {code}
> 12:49:33,513 ERROR [stderr] (Weld Thread Pool -- 4) java.lang.RuntimeException: java.lang.NullPointerException
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:49)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.getProviderFactory(ResteasyClientBuilder.java:362)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:395)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:38)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.load(ResteasyClientEventObserver.java:28)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.observeAsync(ResteasyClientEventObserver.java:23)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.reflect.Method.invoke(Method.java:498)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:109)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.util.Observers.notify(Observers.java:166)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.notifyAsyncObserver(ObserverNotifier.java:413)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$notifyAsyncObservers$5(ObserverNotifier.java:356)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$null$8(ObserverNotifier.java:438)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.security.spi.SecurityServices.lambda$getSecurityContextAssociator$0(SecurityServices.java:80)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$createSupplier$9(ObserverNotifier.java:435)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1590)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.Thread.run(Thread.java:748)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) Caused by: java.lang.NullPointerException
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:60)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:45)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) ... 28 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11907) NPE trying to use Resteasy Client inside CDI Async Event
by Matěj Novotný (Jira)
[ https://issues.jboss.org/browse/WFLY-11907?page=com.atlassian.jira.plugin... ]
Matěj Novotný reassigned WFLY-11907:
------------------------------------
Assignee: Ronald Sigal (was: Matěj Novotný)
> NPE trying to use Resteasy Client inside CDI Async Event
> --------------------------------------------------------
>
> Key: WFLY-11907
> URL: https://issues.jboss.org/browse/WFLY-11907
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 14.0.0.Final, 16.0.0.Final
> Reporter: Cody Lerum
> Assignee: Ronald Sigal
> Priority: Major
>
> When attempting to use the Resteasy Client inside a CDI Async Event a NPE is thrown.
> {code}
> 12:49:33,513 ERROR [stderr] (Weld Thread Pool -- 4) java.lang.RuntimeException: java.lang.NullPointerException
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:49)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.getProviderFactory(ResteasyClientBuilder.java:362)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:395)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder.build(ResteasyClientBuilder.java:38)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.load(ResteasyClientEventObserver.java:28)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at com.outjected.demo.ResteasyClientEventObserver.observeAsync(ResteasyClientEventObserver.java:23)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 12:49:33,514 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.reflect.Method.invoke(Method.java:498)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.injection.MethodInvocationStrategy$DefaultMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:109)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
> 12:49:33,515 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.util.Observers.notify(Observers.java:166)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.notifyAsyncObserver(ObserverNotifier.java:413)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$notifyAsyncObservers$5(ObserverNotifier.java:356)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$null$8(ObserverNotifier.java:438)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.security.spi.SecurityServices.lambda$getSecurityContextAssociator$0(SecurityServices.java:80)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.weld.event.ObserverNotifier.lambda$createSupplier$9(ObserverNotifier.java:435)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run$$$capture(CompletableFuture.java:1590)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:49:33,516 ERROR [stderr] (Weld Thread Pool -- 4) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at java.lang.Thread.run(Thread.java:748)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) Caused by: java.lang.NullPointerException
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.registerProviders(RegisterBuiltin.java:60)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) at org.jboss.resteasy.plugins.providers.RegisterBuiltin.register(RegisterBuiltin.java:45)
> 12:49:33,517 ERROR [stderr] (Weld Thread Pool -- 4) ... 28 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months