[JBoss JIRA] (WFCORE-4387) Fix typo in remoting descriptions
by Teresa Miyar Gil (Jira)
Teresa Miyar Gil created WFCORE-4387:
----------------------------------------
Summary: Fix typo in remoting descriptions
Key: WFCORE-4387
URL: https://issues.jboss.org/browse/WFCORE-4387
Project: WildFly Core
Issue Type: Bug
Components: Remoting
Affects Versions: 9.0.0.Beta2
Reporter: Teresa Miyar Gil
Assignee: Teresa Miyar Gil
Some descriptions lack a space on line break:
{code:java}
"authorize-id" => {
"type" => STRING,
"description" => "The SASL authorization ID. Used as authentication user name to use if no authentication CallbackHandler is specifiedand the se
lected SASL mechanism demands a user name.",
....
"heartbeat-interval" => {
"type" => INT,
"description" => "The interval to use for connection heartbeat, in milliseconds. If the connection is idle in the outbound directionfor this amount of time, a ping message will be sent, which will trigger a corresponding reply message.",
"expressions-allowed" => true,
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3787) executable-model build failed because trying to resolve test case in Windows
by Luca Molteni (Jira)
[ https://issues.jboss.org/browse/DROOLS-3787?page=com.atlassian.jira.plugi... ]
Luca Molteni commented on DROOLS-3787:
--------------------------------------
[~tkobayashi] Can you please try it with the latest master?
https://github.com/kiegroup/droolsjbpm-integration/commit/4e75f686bc6b0d6...
Should fix the problem
> executable-model build failed because trying to resolve test case in Windows
> ----------------------------------------------------------------------------
>
> Key: DROOLS-3787
> URL: https://issues.jboss.org/browse/DROOLS-3787
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.18.0.Final, 7.19.0.Final
> Environment: - Windows 2012
> - Windows 7
> Confirmed with some tags
> - 7.14.0.Final-redhat-00004
> - 7.18.0.Final
> - 7.19.0.Final
> - 7.20.0-SNAPSHOT
> Reporter: Toshiya Kobayashi
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: with-test-sources-reproducer.zip
>
>
> Under the condition:
> - Windows
> - executable-model build (mvn clean install -DgenerateModel=YES -DskipTests)
> The build tries to resolve java source under "src/test/java" then failed with the error
> {noformat}
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.20.0-SNAPSHOT:generateModel (default-generateModel) on project
> with-test-sources: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.20.0-SNAPSHOT:generateModel faile
> d: Unable to get KieModule, Errors Existed: Error Messages:
> [ERROR] Message [id=1, level=ERROR, path=src/test/java/com/sample/SampleTest.java, line=15, column=372
> [ERROR] text=Only a type can be imported. org.mockito.Mockito resolves to a package]
> [ERROR] Message [id=2, level=ERROR, path=src/test/java/com/sample/SampleTest.java, line=22, column=563
> [ERROR] text=Mockito cannot be resolved]
> [ERROR] ---
> {noformat}
> It doesn't happen in MacOS/RHEL7
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (WFLY-11907) NPE trying to use Resteasy Client inside CDI Async Event
by Marek Kopecky (Jira)
[ https://issues.jboss.org/browse/WFLY-11907?page=com.atlassian.jira.plugin... ]
Marek Kopecky commented on WFLY-11907:
--------------------------------------
bq. Marek Kopecky what exactly does RestEasy expect from CDI in ResteasyClientBuilder.newBuilder().build();?
Adding [~ron_sigal] (cc [~asoldano]) for this dev question.
> 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: Matej Novotny
> 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)
5 years, 9 months
[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Donato Marrazzo edited comment on DROOLS-3784 at 3/26/19 5:46 PM:
------------------------------------------------------------------
[~uxdlc] I'm not convinced that this is a great benefit. If I understood correctly the context menu is accessible via right click that does not change much the visibility of the feature.
Moreover, it does not change the number of clicks / actions to add a nested element:
1. save the structure node
2. add nested element
3. save nested element
4. add nested element
5. save nested element
etc
Semantically, it's even incorrect! Why should I save something that is not complete? The structure can be saved only when it is completed with all nested element.
When I add a new nested element the structure should be saved again!
The logical sequence of actions is:
1. create the structure node
2. add the nested element
3. add the nested element
4. (repeat for all nested elements)
5. save the structure node
I believe that in terms of graphical metaphor the structure should start with a "nested placeholder" with a label "add nested element", when the user clicks the placeholder the new element appears and the placehoder shift down. Look at the attached screenshot.
!nested.png|thumbnail!
was (Author: dmarrazzo):
[~uxdlc] I'm not convinced that this is a great benefit. If I understood correctly the context menu is accessible via right click that does not change much the visibility of the feature.
Moreover, it does not change the number of click / action to add a nested element:
1. save the structure node
2. add nested element
3. save nested element
4. add nested element
5. save nested element
etc
Semantically, it's even incorrect! Why should I save something that is not complete? The structure can be saved only when it is completed with all nested element.
When I add a new nested element the structure should be saved again!
The logical sequence of action is:
1. create the structure node
2. add the nested element
3. add the nested element
4. (repeat for all nested elements)
5. save the structure node
I believe that in terms of graphical metaphor the structure should start with a "nested placeholder" with a label "add nested element", when the user clicks the placeholder the new element appears and the placehoder shift down. Look at the attached screenshot.
!nested.png|thumbnail!
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Donato Marrazzo commented on DROOLS-3784:
-----------------------------------------
[~uxdlc] I'm not convinced that this is a great benefit. If I understood correctly the context menu is accessible via right click that does not change much the visibility of the feature.
Moreover, it does not change the number of click / action to add a nested element:
1. save the structure node
2. add nested element
3. save nested element
4. add nested element
5. save nested element
etc
Semantically, it's even incorrect! Why should I save something that is not complete? The structure can be saved only when it is completed with all nested element.
When I add a new nested element the structure should be saved again!
The logical sequence of action is:
1. create the structure node
2. add the nested element
3. add the nested element
4. (repeat for all nested elements)
5. save the structure node
I believe that in terms of graphical metaphor the structure should start with a "nested placeholder" with a label "add nested element", when the user clicks the placeholder the new element appears and the placehoder shift down. Look at the attached screenshot.
!nested.png|thumbnail!
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type
by Donato Marrazzo (Jira)
[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ]
Donato Marrazzo updated DROOLS-3784:
------------------------------------
Attachment: nested.png
> Increase the advanced user productivity when he creates a new Data Type
> -----------------------------------------------------------------------
>
> Key: DROOLS-3784
> URL: https://issues.jboss.org/browse/DROOLS-3784
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.18.0.Final
> Reporter: Donato Marrazzo
> Assignee: Elizabeth Clayton
> Priority: Minor
> Labels: drools-tools
> Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, nested.png, type-selector.png
>
>
> The Data Type editor could be improved in terms of productivity and usability.
> Ideally, the user should be able to create a complex type minimizing the mouse usage.
> 1) Saving the node is an overhead for basic data type (e.g. age: number)
> 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete.
> 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months