[JBoss JIRA] (DROOLS-4258) DMN UX - overlay information about a single scenario run
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4258?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-4258:
-------------------------------------------
[~danielezonca][~tirelli] I posted an updated click-thru. It replaces the buttons with links, and uses a notification message. I combined both the whole and single scenario workflows in the same click-thru. [~bdellasc] is working on the visuals - so the icons used and some of the finer points on colors etc is pending.
> DMN UX - overlay information about a single scenario run
> --------------------------------------------------------
>
> Key: DROOLS-4258
> URL: https://issues.jboss.org/browse/DROOLS-4258
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Daniele Zonca
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
>
> Related to https://issues.jboss.org/browse/DROOLS-3731
> This task will cover this use case:
> - user creates a DMN model
> - user creates a Test Scenario with some scenarios
> - user executes the Test Scenario
> - user open Coverage Report
> - user wants to analyze the execution of a *single scenario* in the DMN model
> - user clicks on "a link" related to the scenario to analyze
> - user lands on DMN editor with overlay information about decision executed, decision failed and for each decision the possibility see actual and expected value (from the scenario) and to open an executed decision table to see which row has been evaluated
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ]
Brian Dellascio resolved DROOLS-4449.
-------------------------------------
Resolution: Done
> Visual design enhancements: Scenario/DMN error overlays
> -------------------------------------------------------
>
> Key: DROOLS-4449
> URL: https://issues.jboss.org/browse/DROOLS-4449
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
> Attachments: ban-solid.svg, check-circle-regular.svg, check-circle-solid.svg, exclamation-circle-regular.svg, exclamation-circle-solid.svg
>
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Verification conditions:
> - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN)
> - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ]
Brian Dellascio commented on DROOLS-4449:
-----------------------------------------
The Marvel handoff mode should give you colors and line thicknesses of the overlay treatments in the mockups. Let me know if you have any additional questions.
[https://marvelapp.com/7cjbjgb/screen/61376985/handoff|https://marvelapp.c...]
Also, here are the SVG icons for each of the overlay states. According to FontAwesome, we must "give appropriate credit, provide a [link to the license|https://fontawesome.com/license], and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use":
* [^ban-solid.svg] - needs FontAwesome attribution
* [^check-circle-regular.svg] - needs FontAwesome attribution
* [^check-circle-solid.svg] - needs FontAwesome attribution
* [^exclamation-circle-solid.svg] - needs FontAwesome attribution
* [^exclamation-circle-regular.svg] - needs FontAwesome attribution, but was also modified/created from other existing FontAwesome icons
The icons should be proportionally scaled to 16px high.
CC [~uxdlc]
> Visual design enhancements: Scenario/DMN error overlays
> -------------------------------------------------------
>
> Key: DROOLS-4449
> URL: https://issues.jboss.org/browse/DROOLS-4449
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
> Attachments: ban-solid.svg, check-circle-regular.svg, check-circle-solid.svg, exclamation-circle-regular.svg, exclamation-circle-solid.svg
>
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Verification conditions:
> - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN)
> - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12063:
-----------------------------------------
WFLY-12546 (the Byte Buddy upgrade) is now in. I kicked off a run of our JDK 13 job at https://ci.wildfly.org/viewLog.html?buildId=168036&tab=buildResultsDiv&bu.... If that comes up clean, or at least with nothing related to this, then this can be resolved.
Thanks, [~gbadner]!
> ClassFormatError on JDK13
> -------------------------
>
> Key: WFLY-12063
> URL: https://issues.jboss.org/browse/WFLY-12063
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Richard Opalka
> Assignee: Scott Marlow
> Priority: Critical
> Labels: blocker-WF18, jdk13
> Attachments: server.log, test.log
>
>
> The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly.
> Affected tests are:
> ---
> [ERROR] Errors:
> [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment
> [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment
> [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment
> [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment
> [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment
> [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy...
> [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment
> [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment
> [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14
> ---
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12558) Intermittent failures in TCPSyslogAuditLogTestCase
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12558?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12558:
-----------------------------------------
A likely fix is to configure the 'reconnect-attempts' attribute on the resource.
> Intermittent failures in TCPSyslogAuditLogTestCase
> --------------------------------------------------
>
> Key: WFLY-12558
> URL: https://issues.jboss.org/browse/WFLY-12558
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Brian Stansberry
> Assignee: Darran Lofthouse
> Priority: Major
>
> 5 tests in TCPSyslogAuditLogTestCase are frequently failing since late August:
> https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=...
> Initial failure has this in the server log:
> {code}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("syslog-audit-log" => "TCPSyslogAuditLogTestCase")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.TCPSyslogAuditLogTestCase" => "WFLYELY00004: Unable to start the service.
> Caused by: java.io.IOException: ELY12001: The maximum reconnect attempts value of 0 was reached. The syslog endpoint will be shutdown."}}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4449) Visual design enhancements: Scenario/DMN error overlays
by Brian Dellascio (Jira)
[ https://issues.jboss.org/browse/DROOLS-4449?page=com.atlassian.jira.plugi... ]
Brian Dellascio updated DROOLS-4449:
------------------------------------
Attachment: ban-solid.svg
check-circle-regular.svg
check-circle-solid.svg
exclamation-circle-regular.svg
exclamation-circle-solid.svg
> Visual design enhancements: Scenario/DMN error overlays
> -------------------------------------------------------
>
> Key: DROOLS-4449
> URL: https://issues.jboss.org/browse/DROOLS-4449
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Brian Dellascio
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
> Attachments: ban-solid.svg, check-circle-regular.svg, check-circle-solid.svg, exclamation-circle-regular.svg, exclamation-circle-solid.svg
>
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Verification conditions:
> - Review interaction design wireframes and click-thrus to offer recommendations for a consistent presentation for error overlays for the two editors (Scenario and DMN)
> - Wireframes posted at: https://issues.jboss.org/browse/DROOLS-4257 and https://issues.jboss.org/browse/DROOLS-3953.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12558) Intermittent failures in TCPSyslogAuditLogTestCase
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12558:
---------------------------------------
Summary: Intermittent failures in TCPSyslogAuditLogTestCase
Key: WFLY-12558
URL: https://issues.jboss.org/browse/WFLY-12558
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
5 tests in TCPSyslogAuditLogTestCase are frequently failing since late August:
https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=...
Initial failure has this in the server log:
{code}
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("syslog-audit-log" => "TCPSyslogAuditLogTestCase")
]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.TCPSyslogAuditLogTestCase" => "WFLYELY00004: Unable to start the service.
Caused by: java.io.IOException: ELY12001: The maximum reconnect attempts value of 0 was reached. The syslog endpoint will be shutdown."}}
{code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFWIP-147) @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFWIP-147?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFWIP-147:
----------------------------------------
[~ehugonnet] [~mnovak] Can this be resolved? If not I think it has to move to WFLY, probably with a priority change.
> @JMSConnectionFactoryDefinition with property resourceAdapater to pooled-connection-factory defined in messaging-active subsystem does not work
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-147
> URL: https://issues.jboss.org/browse/WFWIP-147
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
>
> If pooled-connection-factory is defined in messaging-active subsystem like:
> {code}
> <http-connector name="connector" socket-binding="messaging-socket-binding" endpoint="acceptor" server-name="default"/>
> <pooled-connection-factory name="activemq-ra-remote" entries="java:/testJmsXA " connectors="connector" transaction="xa"/>
> {code}
> and deployment tries to use it to create @JMSConnectionFactoryDefinition like:
> {code}
> @JMSConnectionFactoryDefinition(
> name="java:/jms/myRemoteJmsCf",
> resourceAdapter="activemq-ra-remote")
> {code}
> then deploy fails with:
> {code}
> 13:21:18,284 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mdb-activemq-1.0-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.raactivator.\"mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf\"" => "WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.wildfly.extension.messaging.activemq.ActiveMQResourceAdapter
> Caused by: java.lang.IllegalArgumentException: must provide either TransportType or DiscoveryGroupAddress and DiscoveryGroupPort for ResourceAdapter Connection Factory"}}
> 13:21:18,295 INFO [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "mdb-activemq-1.0-SNAPSHOT.jar" (runtime-name : "mdb-activemq-1.0-SNAPSHOT.jar")
> 13:21:18,297 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.connection-factory.reference-factory.jboss.naming.context.java.jms.myRemoteJmsCf (missing) dependents: [service jboss.naming.context.java.jms.myRemoteJmsCf]
> WFLYCTL0186: Services which failed to start: service jboss.raactivator."mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf": WFLYJCA0046: Failed to start RA deployment [mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_mdb-activemq-1.0-SNAPSHOT_java_/jms/myRemoteJmsCf]
> WFLYCTL0448: 5 additional services are down due to their dependencies being missing or failed
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFWIP-149) Destination not created on remote Artemis broker
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFWIP-149?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFWIP-149:
----------------------------------------
[~ehugonnet] [~mnovak] Can this be resolved? If not I think it has to move to WFLY, probably with a priority change.
> Destination not created on remote Artemis broker
> ------------------------------------------------
>
> Key: WFWIP-149
> URL: https://issues.jboss.org/browse/WFWIP-149
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
>
> JMS Destination is not created on remote broker/cluster if activemq-ra resource adapter is configured to connect to it.
> Test scenario:
> * Start two servers in Artemis cluster (node-1, node-3)
> * Start one more server (node-2) which has configured activemq-ra with initial connectors to remote cluster (node-1, node-3)
> * Deploy MDB with to node-2 with:
> {code}
> @JMSConnectionFactoryDefinition(
> name="java:/jms/myRemoteJmsCf",
> resourceAdapter="activemq-ra")
> @JMSDestinationDefinitions({
> @JMSDestinationDefinition(
> name = "java:/jms/queue/myRemoteOutQueue",
> interfaceName = "javax.jms.Queue",
> resourceAdapter = "activemq-ra",
> destinationName = "myRemoteOutQueue"),
> @JMSDestinationDefinition(
> name = "java:/jms/queue/myRemoteInQueue",
> interfaceName = "javax.jms.Queue",
> resourceAdapter = "activemq-ra",
> destinationName = "myRemoteInQueue")
> })
> {code}
> ** MDB resends messages from myRemoteInQueue to myRemoteOutQueue (send using java:/jms/myRemoteJmsCf)
> * Deploy Servlet to node-2 which uses myRemoteJmsCf to send messages to myRemoteInQueue which are then processed by MDB and re-sent to myRemoteOutQueue
> Expected result: All messages will be in myRemoteOutQueue
> Actual result: No message was processed
> Investigation:
> Problem is that both of the queues were created on node-2 and not in remote artemis cluster (node-1,3)
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months