April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5184) [DMN Designer] Decision table - Propose values from the enumeration constraints

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5184?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5184: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Decision table - Propose values from the enumeration constraints > ------------------------------------------------------------------------------- > > Key: DROOLS-5184 > URL: https://issues.redhat.com/browse/DROOLS-5184 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > > In decision tables often the input values and output values are constrained to a set of options (enumeration). > The DMN spec leverage "output values" and "constraints". > It would be really handy for users to select the value from drop down list. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4930) [DMN Designer] Remove UUID from Alerts panel validation messages

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4930?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4930: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Remove UUID from Alerts panel validation messages > ----------------------------------------------------------------- > > Key: DROOLS-4930 > URL: https://issues.redhat.com/browse/DROOLS-4930 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 07-41-57.png > > > Validation of a DMN diagram can lead to messages being shown in the Alerts Panel. > Stunner is appending the UUID to the message. See [CoreTranslationMessages.getElementValidationMessage()|https://github.com/...] > [~tirelli] has requested their removal. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4033) [DMN Designer] Save Stunners MagnetConnector.auto property

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4033?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4033: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Save Stunners MagnetConnector.auto property > ---------------------------------------------------------- > > Key: DROOLS-4033 > URL: https://issues.redhat.com/browse/DROOLS-4033 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Fix For: 7.21.0.Final > > Attachments: before-saved.png, re-opened.png > > > Further to DROOLS-3702 we are approximating Stunner's {{MagnetConnector}} _auto_ property when unmarshalling a DMN XML file. > Connectors made using the toolbox (either by adding a connector between two existing nodes or adding a new connected node) are {{auto=true}}. Moving a connector end-point to a Magnet manually (other than "centre") sets {{auto=false}}. It is these situations when re-opening the file can give a different visualisation of the connectors. We need to store the connectors _auto_ property as a DMN extension if we are to ensure re-opening any file preserves the connectors appearance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3614: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3273) [DMN Designer] Literal Expression: Font consistency

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3273?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3273: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Literal Expression: Font consistency > --------------------------------------------------- > > Key: DROOLS-3273 > URL: https://issues.redhat.com/browse/DROOLS-3273 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Reported by [~tirelli]: > {quote} > Literal expressions currently use very different fonts and sizes when editing and when presenting. This looks really odd. Also, if the text of the literal expression goes past the border, it is presented clipped, without any visual clue that the expression was clipped. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3634) [DMN Designer] Decision Table: OutputClause improvements

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3634?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3634: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Decision Table: OutputClause improvements > -------------------------------------------------------- > > Key: DROOLS-3634 > URL: https://issues.redhat.com/browse/DROOLS-3634 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The {{Name}} and {{TypeRef}} of {{OutputClauses}} should be components of the parents {{TypeRef}}. For example a {{Decision}} has a {{TypeRef}} of {{tPerson}} that is a structure with fields {{age}}/{{number}} and {{name}}/{{string}}. {{OutputClause}}'s should be defined for {{age}}/{{number}} and {{name}}/{{string}} by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2402) SOS report

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2402: -------------------------------- This could be done in a separate protocol ({{SOS)}}? It would be configurable with a time interval and a list of protocols and their attributes to be fetched. This list could be updated by reading them from an external list. > SOS report > ---------- > > Key: JGRP-2402 > URL: https://issues.redhat.com/browse/JGRP-2402 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > Add the ability to dump the most important attributes to a file / log (configurable), e.g.: > * Max threads > * Number of rejected messages > * Size of retransmission tables (NAKACK2, UNICAST3) > This should be done periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. > These files can then be sent to support via an SOS report. > This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3777) Receiving error IndexOutOfBoundsException on jdk11

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3777?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3777: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > Receiving error IndexOutOfBoundsException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3777 > URL: https://issues.redhat.com/browse/DROOLS-3777 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools, jdk11 > Attachments: Error log array > > > There is IndexOutOfBoundsException on AddInputClauseCommandTest and AddOutputClauseCommandTest if they are run on jdk 11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13126) Refactor EJB client affinity processing

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13126?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13126: ----------------------------------- [~rchakrab] this is a major refactoring and Richard has been working on it. [~rachmato] can you link the Analysis Document PR (which should contain more details)? > Refactor EJB client affinity processing > --------------------------------------- > > Key: WFLY-13126 > URL: https://issues.redhat.com/browse/WFLY-13126 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Cheng Fang > Assignee: Richard Achmatowicz > Priority: Major > Labels: EAP-CD20 > > Refactor of jboss-ejb-client internal operation: change the way in which proxy affinity (an object that decides on which node invocation should be performed) is determined. Instead of calculating it on client side we would let server set the affinity when necessary and propagate it to the client. > This refactor is supposed to reduce the complexity of jboss-ejb-client code and as a result, make it significantly easier to maintain. Richard has prepared a comprehensive document describing the suggested modifications: https://mojo.redhat.com/docs/DOC-1204767 > Parallelly, the test suite has to be refactored to make it compatible with the new algorithm and to provide broad coverage of jboss-ejb-client operation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11442) Remove unused dependencies from org.jboss.as.ejb3

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-11442?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty updated WFLY-11442: --------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13164 > Remove unused dependencies from org.jboss.as.ejb3 > ------------------------------------------------- > > Key: WFLY-11442 > URL: https://issues.redhat.com/browse/WFLY-11442 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Yeray Borges Santana > Assignee: Ranabir Chakraborty > Priority: Major > > Initial analisys checking only first level dependencies from the resource exposed by {{org.jboss.as.ejb3}} shows that these dependencies are being unused: > * org.jboss.jts > * org.wildfly.security.elytron-web.undertow-server > * org.jboss.as.weld > * org.wildfly.clustering.marshalling.spi > * org.wildfly.clustering.marshalling.api > * org.wildfly.client.config > * org.hibernate > The task here is verify that they are not used by any other machanism besides of being a first level dependency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020