December 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3364) Remove from scenario editor Data Objects tab if user is testing DMN

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3364?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3364. ------------------------------------ Resolution: Done Resolved on the DMN tasks. > Remove from scenario editor Data Objects tab if user is testing DMN > ------------------------------------------------------------------- > > Key: DROOLS-3364 > URL: https://issues.jboss.org/browse/DROOLS-3364 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > Data object tab should not be available if the scesim has been created for DMN testing -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3098: ------------------------------------- [~gabriolo] [~danielezonca][~ibek] [~tirelli] [~aglass] Thanks for the summary. Although, from my perspective they are three different solutions - the only commonality they have is that they all might be presented in a pop-over, or a layered dialog of some sort. Let me summarize the 3 options from my perspective: # 1. Rich text editor - incorporate rich text editor features with "smart" selections and pre-selections. # 2. Variant of DMN data type list, which leverages this PatternFly pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/ # 3. Grid view: Presented a nested grid (like the DMN decision table) to both visualize nested structures and allow inputs. My take-away from our meeting, was that you and Ivo aligned on no. 1 as the preferred solution. From my perspective, all three are viable but each has its pros/cons which we discussed in the meeting are touched on in the doc I posted ^^. I can't speak to the CSS/HTML aspect - so I'm including [~srambach] > UX: Add support for data object List > ------------------------------------ > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Ivo Bek > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps. > Preconditions: New feature of current implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-3098 at 12/10/18 10:33 AM: ---------------------------------------------------------------- [~gabriolo] [~danielezonca][~ibek] [~tirelli] [~aglass] Thanks for the summary. Although, from my perspective they are three different solutions - the only commonality they have is that they all might be presented in a pop-over, or a layered dialog of some sort. Let me summarize the 3 options from my perspective: # Rich text editor - incorporate rich text editor features with "smart" selections and pre-selections. # Variant of DMN data type list, which leverages this PatternFly pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/ # Grid view: Presented a nested grid (like the DMN decision table) to both visualize nested structures and allow inputs. My take-away from our meeting, was that you and Ivo aligned on no. 1 as the preferred solution. From my perspective, all three are viable but each has its pros/cons which we discussed in the meeting are touched on in the doc I posted ^^. I can't speak to the CSS/HTML aspect - so I'm including [~srambach] was (Author: uxdlc): [~gabriolo] [~danielezonca][~ibek] [~tirelli] [~aglass] Thanks for the summary. Although, from my perspective they are three different solutions - the only commonality they have is that they all might be presented in a pop-over, or a layered dialog of some sort. Let me summarize the 3 options from my perspective: # 1. Rich text editor - incorporate rich text editor features with "smart" selections and pre-selections. # 2. Variant of DMN data type list, which leverages this PatternFly pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/ # 3. Grid view: Presented a nested grid (like the DMN decision table) to both visualize nested structures and allow inputs. My take-away from our meeting, was that you and Ivo aligned on no. 1 as the preferred solution. From my perspective, all three are viable but each has its pros/cons which we discussed in the meeting are touched on in the doc I posted ^^. I can't speak to the CSS/HTML aspect - so I'm including [~srambach] > UX: Add support for data object List > ------------------------------------ > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Ivo Bek > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps. > Preconditions: New feature of current implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3234) Add a Donut widget to improve the visualisation of test report screen

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3234?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3234: -------------------------------------- Yes. This has been a time sink. Best to not let it drain more time out of us. > Add a Donut widget to improve the visualisation of test report screen > --------------------------------------------------------------------- > > Key: DROOLS-3234 > URL: https://issues.jboss.org/browse/DROOLS-3234 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Attachments: donut.png, pie2b.png, screencast-04-12-18.webm > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3098) UX: Add support for data object List

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3098?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3098: ------------------------------------------ [~danielezonca] [~ibek] [~uxdlc] [~tirelli] To sum up things for the ones who could not attend the meeting. >From my point of view, there is no substantial difference between the three proposals: they all use a popup to insert data; behind the look-and-feel - that is a matter of how html/css is written - they share the same structure/behavior. What is specific in Ivo's proposal (#1) - copy-and-paste of data from an external notepad (for ex) - is not doable in the short terms. Last, probably I was not clear enough on that: since I am not an html/css designer, what I can do now is use the java code with the current css to create a popup with the inner structure/behavior of the required one: surely it will be completely different from what Ivo showed us, and it will "somehow" remember a "patternfly" form. Fell free to ask for further clarifications, if needed. > UX: Add support for data object List > ------------------------------------ > > Key: DROOLS-3098 > URL: https://issues.jboss.org/browse/DROOLS-3098 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Ivo Bek > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > As user I want to be able to use Data Objects that contain Lists and Maps. > Preconditions: New feature of current implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11

by Francesco Nigro (Jira)

[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ] Francesco Nigro commented on WFLY-11026: ---------------------------------------- [~iweiss] Nice one! So the latest changes I have put into 2.7.0 seems to work for JDK 11 too (that's not so distant) (y) > Journal compacting doesn't work with JDK 11 > ------------------------------------------- > > Key: WFLY-11026 > URL: https://issues.jboss.org/browse/WFLY-11026 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Environment: {noformat} > java 11-ea 2018-09-25 > Java(TM) SE Runtime Environment 18.9 (build 11-ea+21) > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {noformat} > Reporter: Martin Styk > Assignee: Ingo Weiss > Priority: Critical > Labels: Java11, jdk10, jdk11 > > Journal compacting doesn't work with Artemis 1.5 and JDK 11 > It fails with following stack trace: > {noformat} > 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77) > at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalArgumentException: duplicate or slice > at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238) > {noformat} > This causes issues also in scenario with journal replication. > {noformat} > 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3234) Add a Donut widget to improve the visualisation of test report screen

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3234?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3234: ------------------------------------- Thanks for tracking this [~kkufova]. > Add a Donut widget to improve the visualisation of test report screen > --------------------------------------------------------------------- > > Key: DROOLS-3234 > URL: https://issues.jboss.org/browse/DROOLS-3234 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Attachments: donut.png, pie2b.png, screencast-04-12-18.webm > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11491) Upgrade Infinispan to 9.4.4.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11491: ----------------------------------- Summary: Upgrade Infinispan to 9.4.4.Final Key: WFLY-11491 URL: https://issues.jboss.org/browse/WFLY-11491 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 15.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro https://issues.jboss.org/projects/ISPN/versions/12340019 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3420) Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3420: ---------------------------------------- Summary: Replace Composite for SourceTypeSelector/TitledAttachmentFileWidget Key: DROOLS-3420 URL: https://issues.jboss.org/browse/DROOLS-3420 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi SourceTypeSelector and TitledAttachmentFileWidget extends Composite, while we are currently strive to move toward new Elemental. At the same time, the list where they are using is expecting a IsWidget type. So, try if already a similar widget exists inside appformer/kie, otherwise create new one and (eventually) implement the asWidget method and returns a "Widget". Later, ask [~Rikkola] to move it on upper framework. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3419) Bump heap size for findbugs in drools-compiler Maven build

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3419?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3419: ----------------------------------- Sprint: 2018 Week 48-50 > Bump heap size for findbugs in drools-compiler Maven build > ---------------------------------------------------------- > > Key: DROOLS-3419 > URL: https://issues.jboss.org/browse/DROOLS-3419 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > FindBugs is crashing with OutOfMemory error. Known issue, we just need to add more memory. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2018