May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10398) The Hibernate Search/ORM JBoss Module need a dependency on javax.enterprise.api

by Sanne Grinovero (JIRA)

Sanne Grinovero created WFLY-10398: -------------------------------------- Summary: The Hibernate Search/ORM JBoss Module need a dependency on javax.enterprise.api Key: WFLY-10398 URL: https://issues.jboss.org/browse/WFLY-10398 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 13.0.0.CR1 The EE8 version of the Hibernate Search module now depends on {{javax.enterprise.api}} as well. We missed to add this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2551) Executable model - tests from package "integrationtests.operators" fail when run with executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2551?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-2551: ----------------------------------- Assignee: Luca Molteni (was: Mario Fusco) > Executable model - tests from package "integrationtests.operators" fail when run with executable model > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2551 > URL: https://issues.jboss.org/browse/DROOLS-2551 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Luca Molteni > > When running tests from package org.drools.compiler.integrationtests.operators [1] with executable model, many of them fail (~120 out of ~520). To run the tests with the model, I moved the tests to a separate module in this PR [2], please check the PR description to see how to run them. > [1] https://github.com/kiegroup/drools/tree/d7ad4fb31647b5295c3cbc0321f0d8f89... > [2] https://github.com/kiegroup/drools/pull/1901 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1964) [DMN Editor] Input Data typeRef

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1964?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-1964: ---------------------------------------- Hi [~jomarko] I've split work into sub-tasks to make things (hopefully) easier to follow!? https://issues.jboss.org/browse/DROOLS-2563 is a large task in it's own right and may be split further when I get to it. > [DMN Editor] Input Data typeRef > ------------------------------- > > Key: DROOLS-1964 > URL: https://issues.jboss.org/browse/DROOLS-1964 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: reported-by-qe > > The Input Data nodes specifies the datatype via _typeRef_ attribute. Allowed are simple datatypes, enumerations of allowed values and complex data types like Person. > During work on this were added *typeRef* selection widgets for three DMN nodes: BKM, Decision, and Input. These selection widgets offer [BuiltInType|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-..., data types of project, editor for allowed values (enumerations). > h2. Acceptance test > - Load dmn from other tool, check data types recognized appropriately, can be edited, saved, reopened > - Create new dmn, define different data types for different nodes, save, reopen, check values preserved -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2543) "?" doesn't work with multi-conditions in decision table

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2543?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-2543: -------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > "?" doesn't work with multi-conditions in decision table > -------------------------------------------------------- > > Key: DROOLS-2543 > URL: https://issues.jboss.org/browse/DROOLS-2543 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Matteo Mortari > > When having multivalue cell in DMN decision table with this values: "? > 10, 90", FEEL compilation fails with the following output [1]. This multivalue works when it is closed in brackets like this: "(? > 10), 90" or when the condition order is switched like this: "90, ? > 10". > Reproducer can be found here [2]. > [1] https://gist.github.com/baldimir/d6f51198696e4f2b84d3eb0aaf2a9815 > [2] https://github.com/kiegroup/drools/pull/1898/files#diff-388002c5a2500f2ec... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-39) Regression in JMS bridge with network failures tests

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-39?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-39: ---------------------------------- [~kabirkhan] I moved it to WFWIP as this occurs with Artemis 2.x upgrade. > Regression in JMS bridge with network failures tests > ---------------------------------------------------- > > Key: WFWIP-39 > URL: https://issues.jboss.org/browse/WFWIP-39 > Project: WildFly WIP > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq > Attachments: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip > > > *Scenario* > Node A and B are started. JMS bridge with {{once and only once}} delivery and 1 reconnect attempt is deployed on node A. Producer starts sending mix of normal and large messages to InQueue on node A. Jms bridge resends messages from A's InQueue to B's OutQueue. During this time short network failure sequence (network goes down and then up) is executed twice. Receiver receives messages from OutQueue(also from node A). After that, network stays disconnected. Another receiver receives remaining messages from A's InQueue. > {noformat:title=Jms Bridge} > <jms-bridge name="myBridge" module="org.apache.activemq.artemis" quality-of-service="ONCE_AND_ONLY_ONCE" failure-retry-interval="1000" max-retries="1" max-batch-size="10" max-batch-time="100" add-messageID-in-header="true"> > <source connection-factory="java:/ConnectionFactory" destination="jms/queue/InQueue"/> > <target connection-factory="jms/BridgeConnectionFactory" destination="jms/queue/OutQueue"> > <target-context> > <property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/> > <property name="java.naming.provider.url" value="http-remoting://127.0.0.1:9080"/> > </target-context> > </target> > </jms-bridge> > {noformat} > *Issue* > * node A's InQueue and node B's OutQueue is empty > * There are no prepared transactions on node A > * some messages *are missing* after test (multiply of 10, which is number of messages in one transaction) > * this scenario fails *intermittently* > 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) > Logs are attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2566) [DMN Editor] Integrate Editor into Workbench

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2566: -------------------------------------- Summary: [DMN Editor] Integrate Editor into Workbench Key: DROOLS-2566 URL: https://issues.jboss.org/browse/DROOLS-2566 Project: Drools Issue Type: Feature Request Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis Following https://issues.jboss.org/browse/DROOLS-2565 we can integrate the DMN Editor into the Workbench - adding support to enable/disable the Editor (disabled by default). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-39) Regression in JMS bridge with network failures tests

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-39?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil moved WFLY-10115 to WFWIP-39: ----------------------------------------- Project: WildFly WIP (was: WildFly) Key: WFWIP-39 (was: WFLY-10115) Component/s: JMS (was: JMS) > Regression in JMS bridge with network failures tests > ---------------------------------------------------- > > Key: WFWIP-39 > URL: https://issues.jboss.org/browse/WFWIP-39 > Project: WildFly WIP > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq > Attachments: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip > > > *Scenario* > Node A and B are started. JMS bridge with {{once and only once}} delivery and 1 reconnect attempt is deployed on node A. Producer starts sending mix of normal and large messages to InQueue on node A. Jms bridge resends messages from A's InQueue to B's OutQueue. During this time short network failure sequence (network goes down and then up) is executed twice. Receiver receives messages from OutQueue(also from node A). After that, network stays disconnected. Another receiver receives remaining messages from A's InQueue. > {noformat:title=Jms Bridge} > <jms-bridge name="myBridge" module="org.apache.activemq.artemis" quality-of-service="ONCE_AND_ONLY_ONCE" failure-retry-interval="1000" max-retries="1" max-batch-size="10" max-batch-time="100" add-messageID-in-header="true"> > <source connection-factory="java:/ConnectionFactory" destination="jms/queue/InQueue"/> > <target connection-factory="jms/BridgeConnectionFactory" destination="jms/queue/OutQueue"> > <target-context> > <property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/> > <property name="java.naming.provider.url" value="http-remoting://127.0.0.1:9080"/> > </target-context> > </target> > </jms-bridge> > {noformat} > *Issue* > * node A's InQueue and node B's OutQueue is empty > * There are no prepared transactions on node A > * some messages *are missing* after test (multiply of 10, which is number of messages in one transaction) > * this scenario fails *intermittently* > 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) > Logs are attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2563: ----------------------------------- Tester: Jozef Marko > [DMN Editor] Add support to define data-types > --------------------------------------------- > > Key: DROOLS-2563 > URL: https://issues.jboss.org/browse/DROOLS-2563 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Add support for the User to define data-types ({{ItemDefinition}}. > This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2564) [DMN Editor] Add to use data-types on applicable Expression types

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2564?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2564: ----------------------------------- Tester: Jozef Marko > [DMN Editor] Add to use data-types on applicable Expression types > ----------------------------------------------------------------- > > Key: DROOLS-2564 > URL: https://issues.jboss.org/browse/DROOLS-2564 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Different types of Expression (the grid-view) should support defining the input and output data-types. I am leaving implementation of this until the ability to use and define data-types at the graph-view is fully complete; as the scenarios required by this JIRA will re-use the same components. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10115) Regression in JMS bridge with network failures tests

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10115?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-10115: ----------------------------------- [~jmesnil] [~martyn-taylor] - I'd hazard a guess and say this is a blocker for 7.2.0.GA rather than CD13? > Regression in JMS bridge with network failures tests > ---------------------------------------------------- > > Key: WFLY-10115 > URL: https://issues.jboss.org/browse/WFLY-10115 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Martin Styk > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq > Attachments: org.jboss.qa.hornetq.test.bridges.NetworkFailuresJMSBridgesTestCase.zip > > > *Scenario* > Node A and B are started. JMS bridge with {{once and only once}} delivery and 1 reconnect attempt is deployed on node A. Producer starts sending mix of normal and large messages to InQueue on node A. Jms bridge resends messages from A's InQueue to B's OutQueue. During this time short network failure sequence (network goes down and then up) is executed twice. Receiver receives messages from OutQueue(also from node A). After that, network stays disconnected. Another receiver receives remaining messages from A's InQueue. > {noformat:title=Jms Bridge} > <jms-bridge name="myBridge" module="org.apache.activemq.artemis" quality-of-service="ONCE_AND_ONLY_ONCE" failure-retry-interval="1000" max-retries="1" max-batch-size="10" max-batch-time="100" add-messageID-in-header="true"> > <source connection-factory="java:/ConnectionFactory" destination="jms/queue/InQueue"/> > <target connection-factory="jms/BridgeConnectionFactory" destination="jms/queue/OutQueue"> > <target-context> > <property name="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/> > <property name="java.naming.provider.url" value="http-remoting://127.0.0.1:9080"/> > </target-context> > </target> > </jms-bridge> > {noformat} > *Issue* > * node A's InQueue and node B's OutQueue is empty > * There are no prepared transactions on node A > * some messages *are missing* after test (multiply of 10, which is number of messages in one transaction) > * this scenario fails *intermittently* > 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) > Logs are attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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