[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3330:
--------------------------------
Description:
Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Rationale:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
was:
Creating this jira to investigate if it would be possible to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
Rationale:
* As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
* The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
* If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
> DMN Properties panel - Style menu
> ---------------------------------
>
> Key: DROOLS-3330
> URL: https://issues.jboss.org/browse/DROOLS-3330
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Michael Anstis
> Priority: Optional
> Labels: UX, UXTeam, drools-tools
> Attachments: styles.png
>
>
> Request to combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu.
> Rationale:
> * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest.
> * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties.
> * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 weeks, 1 day
[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 months
[JBoss JIRA] (WFLY-10796) Warning about JSF version 'NONE' is shown in logs
by Jan Kašík (JIRA)
[ https://issues.jboss.org/browse/WFLY-10796?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-10796:
-----------------------------
Description:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
was:
Following warning is shown in log upon server start:
{code}
2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
{code}
Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present.
> Warning about JSF version 'NONE' is shown in logs
> --------------------------------------------------
>
> Key: WFLY-10796
> URL: https://issues.jboss.org/browse/WFLY-10796
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 14.0.0.Beta2
> Reporter: Jan Kašík
> Assignee: Dmitrii Tikhomirov
>
> Following warning is shown in log upon server start:
> {code}
> 2018-08-02 16:13:28,487 WARN [org.jboss.as.jsf] (MSC service thread 1-3) WFLYJSF0005: Unknown JSF version 'NONE'. Default version 'main' will be used instead.
> {code}
> Seems like, that 'NONE' constant from WildFly code is somehow used instead of default 'main' value. Version 'NONE' is not specified anywhere, so this warning should not be present. From my point of view, it seems like I am trying set slot 'NONE' to be the default. But nothing like that is happening.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
2 months, 3 weeks
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-11720:
-----------------------------------
Opened PR for WEJBHTTP-24 and EJBCLIENT-323 to upgrade jboss-marshalling in wildfly-http-client and jboss-ejb-client.
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Assignee: Cheng Fang
> Priority: Critical
> Attachments: classes.zip, client-app.zip
>
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-11800) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
Cheng Fang created WFLY-11800:
---------------------------------
Summary: Cannot invoke EJB over HTTP on JDK 11
Key: WFLY-11800
URL: https://issues.jboss.org/browse/WFLY-11800
Project: WildFly
Issue Type: Bug
Components: EJB, Remoting
Affects Versions: 16.0.0.Beta1
Environment: JDK 11
Reporter: Cheng Fang
Assignee: Cheng Fang
Run of client app calling EJB over HTTP fails on JDK 11 with following log:
{noformat}
Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.6.Final
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.1.3.Final
Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 4.0.2.Final
Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.0.Beta2
Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.0.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
java.lang.ExceptionInInitializerError
at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
... 9 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (WFLY-11799) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
Cheng Fang created WFLY-11799:
---------------------------------
Summary: Cannot invoke EJB over HTTP on JDK 11
Key: WFLY-11799
URL: https://issues.jboss.org/browse/WFLY-11799
Project: WildFly
Issue Type: Bug
Components: EJB, Remoting
Affects Versions: 16.0.0.Beta1
Environment: JDK 11
Reporter: Cheng Fang
Assignee: Cheng Fang
Run of client app calling EJB over HTTP fails on JDK 11 with following log:
{noformat}
Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.6.Final
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.1.3.Final
Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
INFO: JBoss EJB Client version 4.0.2.Final
Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.6.5.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.0.Beta2
Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.0.Final
Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
java.lang.ExceptionInInitializerError
at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
... 9 more
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (DROOLS-3077) Enhance data type restrictions UX - Decision Table/properties
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3077?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3077:
-------------------------------------
[~karreiro] [~manstis]
The latest direction for the Input Clause pop-over is:
https://redhat.invisionapp.com/share/8BQRVFUVU3Z#/349667215_Input1
(this is a rough version, still need to do some clean-up, but it shows the basic flow). The basic changes are as follows:
* Explicit Save/Cancel buttons.
* If user enters a Data Type that has constraints already applied to them, they are displayed as read-only. The user will need Add more constraints by going through the Data Type (a story for another sprint.) In this case on the Manage link is available for that action.
* If the user select a type without constraints, then they can add constraints via this pop-over. The otherwise hidden Action to Add is enabled (presented). Clicking that will open a dialog for just adding to the Input clause. The user enter the values and round-trip back to the pop-over for confirmation before saving. Once saved the table is updated. Wdyt?
> Enhance data type restrictions UX - Decision Table/properties
> -------------------------------------------------------------
>
> Key: DROOLS-3077
> URL: https://issues.jboss.org/browse/DROOLS-3077
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-28 at 2.44.59 PM.png, date-time.png, date.png, enumration-widget.png, pop-overc.png, pop-overcSpecs.png, read-mode.png, select.png, time.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
