November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-3330: ---------------------------------- Attachment: ChlamydiaScreening_CQM.jpg > 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: ChlamydiaScreening_CQM.jpg, 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Edson Tirelli edited comment on DROOLS-3330 at 11/21/18 8:55 PM: ----------------------------------------------------------------- If it is not a problem, I would like to keep the ability to customize the node colours. This is important in DMN because contrary to BPMN, there are only 3 nodes in DMN and no custom tasks or icons. This way colours are used to differentiate sets of nodes that have a related concern. For instance, the following example from a Clinical Decision Support use case uses colours to make the model more readable. !ChlamydiaScreening_CQM.jpg|thumbnail! was (Author: tirelli): If it is not a problem, I would like to keep the ability to customize the node colours. This is important in DMN because contrary to BPMN, there are only 3 nodes in DMN and no custom tasks or icons. This way colours are used to differentiate sets of nodes that have a related concern. For instance, the following example from a Clinical Decision Support use case uses colours to make the model more readable. > 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: ChlamydiaScreening_CQM.jpg, 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3330) DMN Properties panel - Style menu

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3330?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3330: --------------------------------------- If it is not a problem, I would like to keep the ability to customize the node colours. This is important in DMN because contrary to BPMN, there are only 3 nodes in DMN and no custom tasks or icons. This way colours are used to differentiate sets of nodes that have a related concern. For instance, the following example from a Clinical Decision Support use case uses colours to make the model more readable. > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11397) SSLException: closing inbound before receiving peer's close_notify

by Radoslav Ivanov (Jira)

Radoslav Ivanov created WFLY-11397: -------------------------------------- Summary: SSLException: closing inbound before receiving peer's close_notify Key: WFLY-11397 URL: https://issues.jboss.org/browse/WFLY-11397 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 14.0.1.Final Reporter: Radoslav Ivanov Assignee: Stefano Maestri Hi Could you give more directions on what is wrong here? {code:java} ...2018 WARN: Caught while disconnecting... 01:40:25,491 ERROR [stderr] (IdleRemover) 01:40:25,491 ERROR [stderr] (IdleRemover) EXCEPTION STACK TRACE: 01:40:25,491 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) ** BEGIN NESTED EXCEPTION ** 01:40:25,492 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) javax.net.ssl.SSLException 01:40:25,492 ERROR [stderr] (IdleRemover) MESSAGE: closing inbound before receiving peer's close_notify 01:40:25,492 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) STACKTRACE: 01:40:25,492 ERROR [stderr] (IdleRemover) 01:40:25,492 ERROR [stderr] (IdleRemover) javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129) 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:308) 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:264) 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:255) 01:40:25,492 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:645) 01:40:25,493 ERROR [stderr] (IdleRemover) at java.base/sun.security.ssl.SSLSocketImpl.shutdownInput(SSLSocketImpl.java:624) 01:40:25,493 ERROR [stderr] (IdleRemover) at com.mysql@5.1.45//com.mysql.jdbc.MysqlIO.quit(MysqlIO.java:2246) 01:40:25,493 ERROR [stderr] (IdleRemover) at com.mysql@5.1.45//com.mysql.jdbc.ConnectionImpl.realClose(ConnectionImpl.java:4236) 01:40:25,493 ERROR [stderr] (IdleRemover) at com.mysql@5.1.45//com.mysql.jdbc.ConnectionImpl.close(ConnectionImpl.java:1462) 01:40:25,493 ERROR [stderr] (IdleRemover) at org.jboss.ironjacamar.jdbcadapters@1.4.11.Final//org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.destroy(BaseWrapperManagedConnection.java:491) 01:40:25,493 ERROR [stderr] (IdleRemover) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.destroy(AbstractConnectionListener.java:637) 01:40:25,493 ERROR [stderr] (IdleRemover) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.removeIdleConnections(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1006) 01:40:25,493 ERROR [stderr] (IdleRemover) at org.jboss.ironjacamar.impl@1.4.11.Final//org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover$IdleRemoverRunner.run(IdleRemover.java:275) 01:40:25,493 ERROR [stderr] (IdleRemover) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 01:40:25,493 ERROR [stderr] (IdleRemover) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 01:40:25,493 ERROR [stderr] (IdleRemover) at java.base/java.lang.Thread.run(Thread.java:834) 01:40:25,493 ERROR [stderr] (IdleRemover) 01:40:25,493 ERROR [stderr] (IdleRemover) 01:40:25,493 ERROR [stderr] (IdleRemover) ** END NESTED EXCEPTION ** {code} Regards Radoslav -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-198) Nonexistent version of org.apache.taglibs referenced in org.jboss.spec

by Karl Nicholas (Jira)

[ https://issues.jboss.org/browse/JBEE-198?page=com.atlassian.jira.plugin.s... ] Karl Nicholas commented on JBEE-198: ------------------------------------ Okay, I did just find the correct version in the developer repository. https://maven.repository.redhat.com/nexus/content/repositories/developer > Nonexistent version of org.apache.taglibs referenced in org.jboss.spec > ---------------------------------------------------------------------- > > Key: JBEE-198 > URL: https://issues.jboss.org/browse/JBEE-198 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-javaee-specs > Affects Versions: JavaEE 7 Spec APIs 1.1.0.Final > Environment: Wildfly 14.0.1.Final BOM (Java 1.8, Windows 10 ... ) > Reporter: Karl Nicholas > Assignee: Scott Marlow > Priority: Major > > Actually, the issue is with "JavaEE 7 Spec APIs 1.1.1.Final" and "JavaEE 8 Spec APIs 1.0.1.Final" but they were not available as listed versions. These are the specs referenced by the Wildfly 14.0.1.Final BOM which I want to use because I want JPA 2.2. > The version in the spec pom is "<version.org.apache.jstl>1.2.6-RC1</version.org.apache.jstl>" but the repository has only 1.2.6.RC1-redhat-1. Same for both versions of the specs above. > See > https://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee-7.0/1.1.1.Fina... > and > https://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee-8.0/1.0.1.Fina... > There is a 1.2.6-RC1 version on "mvnrepository.com" but not one on on search.maven.org or any redhat repository. Since this is early adopter stuff I think there should be correct versions on https://maven.repository.redhat.com/earlyaccess and probably on search.maven.org since I can get the Wildfly.14.0.1.Final bom from there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-198) Nonexistent version of org.apache.taglibs referenced in org.jboss.spec

by Karl Nicholas (Jira)

Karl Nicholas created JBEE-198: ---------------------------------- Summary: Nonexistent version of org.apache.taglibs referenced in org.jboss.spec Key: JBEE-198 URL: https://issues.jboss.org/browse/JBEE-198 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-javaee-specs Affects Versions: JavaEE 7 Spec APIs 1.1.0.Final Environment: Wildfly 14.0.1.Final BOM (Java 1.8, Windows 10 ... ) Reporter: Karl Nicholas Assignee: Scott Marlow Actually, the issue is with "JavaEE 7 Spec APIs 1.1.1.Final" and "JavaEE 8 Spec APIs 1.0.1.Final" but they were not available as listed versions. These are the specs referenced by the Wildfly 14.0.1.Final BOM which I want to use because I want JPA 2.2. The version in the spec pom is "<version.org.apache.jstl>1.2.6-RC1</version.org.apache.jstl>" but the repository has only 1.2.6.RC1-redhat-1. Same for both versions of the specs above. See https://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee-7.0/1.1.1.Fina... and https://repo1.maven.org/maven2/org/jboss/spec/jboss-javaee-8.0/1.0.1.Fina... There is a 1.2.6-RC1 version on "mvnrepository.com" but not one on on search.maven.org or any redhat repository. Since this is early adopter stuff I think there should be correct versions on https://maven.repository.redhat.com/earlyaccess and probably on search.maven.org since I can get the Wildfly.14.0.1.Final bom from there. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11396) Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.Final

by Alexey Loubyansky (Jira)

Alexey Loubyansky created WFLY-11396: ---------------------------------------- Summary: Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.Final Key: WFLY-11396 URL: https://issues.jboss.org/browse/WFLY-11396 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Upgrade to the final releases of Galleon and WildFly Galleon plugins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4235) Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.Final

by Alexey Loubyansky (Jira)

Alexey Loubyansky created WFCORE-4235: ----------------------------------------- Summary: Upgrade to Galleon and WildFly Galleon Plugins 3.0.0.Final Key: WFCORE-4235 URL: https://issues.jboss.org/browse/WFCORE-4235 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Upgrade to the final releases of Galleon and WildFly Galleon plugins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-400) Add Tests on Kiali Pyton Client

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-400?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-400: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Add Tests on Kiali Pyton Client > ------------------------------- > > Key: SWSQE-400 > URL: https://issues.jboss.org/browse/SWSQE-400 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Currently, there are no tests on Kiali Python Client. > I think we need add some tests there -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3344) [DMN Designer] Data Types - UX improvements in the Data Type List View

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3344?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-3344: --------------------------------------- Description: Improve the Data Types list view according to the mockups. !DROOLS-3344.png|thumbnail! # Add labels in the edit mode # The kebab menu must be omitted in the edit mode # Rename "Decision Tables" to "Boxed Expressions" # Rename "Collection" to "List" was: Improve the Data Types list view according to the mockups. !DROOLS-3344.png|thumbnail! # Add labels in the edit mode # The kebab menu must be omitted in the edit mode > [DMN Designer] Data Types - UX improvements in the Data Type List View > ---------------------------------------------------------------------- > > Key: DROOLS-3344 > URL: https://issues.jboss.org/browse/DROOLS-3344 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3344.png > > > Improve the Data Types list view according to the mockups. > !DROOLS-3344.png|thumbnail! > # Add labels in the edit mode > # The kebab menu must be omitted in the edit mode > # Rename "Decision Tables" to "Boxed Expressions" > # Rename "Collection" to "List" -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 8 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 November 2018