August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2823) FEEL Parser: `not` breaks with `list contains`

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2823?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2823: ----------------------------------- Sprint: 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 30-32) > FEEL Parser: `not` breaks with `list contains` > ----------------------------------------------- > > Key: DROOLS-2823 > URL: https://issues.jboss.org/browse/DROOLS-2823 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > > *list contains([1,2,3,4,5,6], 3)* returns true > *not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false > Most likely related to an issue with the parse tree branches -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2728) UX for custom data-types

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2728: ----------------------------------- Sprint: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 27-29, 2018 Week 30-32) > UX for custom data-types > ------------------------ > > Key: DROOLS-2728 > URL: https://issues.jboss.org/browse/DROOLS-2728 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png > > > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2716: ----------------------------------- Sprint: 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 27-29, 2018 Week 30-32) > [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated > --------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2716 > URL: https://issues.jboss.org/browse/DROOLS-2716 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > - When the user changes a row in the "Field name" column, the DMN model needs to be updated; > - When the user changes a row in the "Field type" column, the DMN model needs to be updated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2762: ----------------------------------- Sprint: 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 30-32) > [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table) > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2762 > URL: https://issues.jboss.org/browse/DROOLS-2762 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition): > - This component must be disabled (or hidden) when an existing/primitive data type is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2794) [DMN Designer] Data-types: Support usage in grids

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2794?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2794: ----------------------------------- Sprint: 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 30-32) > [DMN Designer] Data-types: Support usage in grids > ------------------------------------------------- > > Key: DROOLS-2794 > URL: https://issues.jboss.org/browse/DROOLS-2794 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > Listing requirements here; and then possibly move this to an EPIC and add smaller tasks. > *_General_* > - (x) {{<< Back to XXX}} does not update if name changed in Properties panel > - (x) "TypeRef" on Properties panel should show "Output Data Type" > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel > *_Decision Table_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Hide Output Data Type in header when there are multiple {{OutputClause}} columns > - (x) {{InputClause}} columns header should show Input Data Type > - (x) {{InputClause}} columns should support changing the Input Data Type > - (x) {{OutputClause}} columns header should show Output Data Type > - (x) {{OutputClause}} columns should support changing the Output Data Type > *_Context_* > - (x) Grid header _could_ show Output Data Type (for Decision/BKM) > - (/) Editing Output Data Type (for Decision/BKM) is possible via Properties panel > - (x) {{ContextEntry}} should show Output Data Type (for {{ContextEntry}}) > - (x) {{ContextEntry}} should support changing the Output Data Type (for {{ContextEntry}}) > *_Relation_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) {{InformationItem}} column should show Input Data Type > - (x) {{InformationItem}} column should support changing Input Data Type > *_Invocation_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2549: ----------------------------------- Sprint: 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32, 2018 Week 33-35 (was: 2018 Week 19-22, 2018 Week 23-24, 2018 Week 25-26, 2018 Week 27-29, 2018 Week 30-32) > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.11.0.Final > > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-85) [Upgrade Artemis 2.x] MDB (Artemis 1.5.x RA) cannot connect to Artemis 2.x broker using JGroups discovery

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/WFWIP-85?page=com.atlassian.jira.plugin.s... ] Yong Hao Gao commented on WFWIP-85: ----------------------------------- Hi [~mnovak], The problem seems to do with JGroups. Any broadcast of artemis connectors from Server1/2 are not received by Server3/4. I noticed that in server1/2 the version of jgroups is 3.6.13, and version used in server3/4 is 4.0.13. I don't know if that will be supported. I'm asking Bela for more information. btw I tried to upgrade 3.6.13 to 4.0.13 and the test won't run anymore. I guess the difference between 2 versions is very big. Howard > [Upgrade Artemis 2.x] MDB (Artemis 1.5.x RA) cannot connect to Artemis 2.x broker using JGroups discovery > --------------------------------------------------------------------------------------------------------- > > Key: WFWIP-85 > URL: https://issues.jboss.org/browse/WFWIP-85 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > MDB deployed to older EAP 7.1.0.GA(Artemis 1.5 RA) cannot consume messages from newer Artemis 2.x server (build https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...) > There is no exception in the log during start however MDB does not start to consume messages. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2872) CSS for test results panel/dock TABS

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2872?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-2872: -------------------------------------- I can. Does master here mean the war created from master? > CSS for test results panel/dock TABS > ------------------------------------ > > Key: DROOLS-2872 > URL: https://issues.jboss.org/browse/DROOLS-2872 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-08-09 at 11.27.12 AM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10827) Exclude hornetq-journal from the transitive depenencies

by Kabir Khan (JIRA)

Kabir Khan created WFLY-10827: --------------------------------- Summary: Exclude hornetq-journal from the transitive depenencies Key: WFLY-10827 URL: https://issues.jboss.org/browse/WFLY-10827 Project: WildFly Issue Type: Bug Components: JMS Reporter: Kabir Khan Assignee: Jeff Mesnil Although not part of the server runtime, the hornetq-journal is included as a transitive dependency. This fixes it: {code} --- pom.xml +++ pom.xml @@ -3920,6 +3920,12 @@ <groupId>org.hornetq</groupId> <artifactId>hornetq-commons</artifactId> <version>\${version.org.hornetq}</version> + <exclusions> + <exclusion> + <groupId>org.hornetq</groupId> + <artifactId>hornetq-journal</artifactId> + </exclusion> + </exclusions> </dependency> <dependency> @@ -3932,6 +3938,12 @@ <groupId>org.hornetq</groupId> <artifactId>hornetq-jms-client</artifactId> <version>\${version.org.hornetq}</version> + <exclusions> + <exclusion> + <groupId>org.hornetq</groupId> + <artifactId>hornetq-journal</artifactId> + </exclusion> + </exclusions> </dependency> <dependency> <groupId>org.infinispan</groupId> @@ -4314,6 +4326,10 @@ <version>\${version.org.jboss.ironjacamar}</version> <exclusions> <exclusion> + <artifactId>ironjacamar-spec-api</artifactId> + <groupId>org.jboss.ironjacamar</groupId> + </exclusion> + <exclusion> <artifactId>jbossxb</artifactId> <groupId>org.jboss</groupId> </exclusion> @@ -4346,6 +4362,10 @@ <version>\${version.org.jboss.ironjacamar}</version> <exclusions> <exclusion> + <groupId>org.jboss.ironjacamar</groupId> + <artifactId>ironjacamar-spec-api</artifactId> + </exclusion> + <exclusion> <artifactId>jboss-integration</artifactId> <groupId>org.jboss.integration</groupId> </exclusion> @@ -4376,6 +4396,10 @@ <version>\${version.org.jboss.ironjacamar}</version> <exclusions> <exclusion> + <groupId>org.jboss.ironjacamar</groupId> + <artifactId>ironjacamar-spec-api</artifactId> + </exclusion> + <exclusion> <artifactId>jboss-common-core</artifactId> <groupId>org.jboss</groupId> </exclusion> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-28) [Artemis 2.x upgrade] Unexptected crash of server in SOAK test

by Otavio Piske (JIRA)

[ https://issues.jboss.org/browse/WFWIP-28?page=com.atlassian.jira.plugin.s... ] Otavio Piske commented on WFWIP-28: ----------------------------------- > Do you have a test where you check native memory allocation for Artemis 2.x and how often it's cleaned by GC cycles? The tests do collect basic JVM memory information, but the GC cycle count is not collected (I can add that, though). We track global/system memory information (along w/ other metrics), but I don't have that information specifically for the broker process. [~mtoth] if you can come up with some basic requirements of what metrics you need to keep track and submit a ticket on [Maestro repository|https://github.com/maestro-performance/maestro-java], I will write the code to support this. > [Artemis 2.x upgrade] Unexptected crash of server in SOAK test > -------------------------------------------------------------- > > Key: WFWIP-28 > URL: https://issues.jboss.org/browse/WFWIP-28 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Francesco Nigro > Priority: Blocker > Labels: feature-branch-blocker > Attachments: sosreport-rvaisdebug.asd-20180807101658.tar.xz > > > After ~13 hours there is unexpected crash of one server in SOAK test. There is no error/warning in the logs. > Test Scenario: > * Start 2 servers > * Client sends messages to input queue. Messages then go through: > * One server to another through MDB reading and sending them from remote container through resource adapter > * Messages are forwarded from one server to another over JMS bridge and back over Core bridge > * Messages have JMSReplyTo defined with a temporary queue, that is filled with responses for the client > * Messages are read from the destination with stateless EJB and sent back to clients > * Client reads the messages after the pass through all the soak modules. > Pass Criteria: In the last step receiver consumes all messages sent by producer. > Actual Result: > After ~13 hours 1st server suddenly crashes. There is no error/warning in server logs. > Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018