April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5271) RHS statements ordering changes with modify block in executable model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5271?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5271: -------------------------------------- Sprint: 2020 Week 16-18 (from Apr 13) > RHS statements ordering changes with modify block in executable model > --------------------------------------------------------------------- > > Key: DROOLS-5271 > URL: https://issues.redhat.com/browse/DROOLS-5271 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > The order of statements in RHS changes with executable model when modify block is involved. The below rule can tell the difference with standard-drl. > {noformat} > import org.drools.modelcompiler.domain.Person;global java.util.List list; > rule R when > $p1 : Person(name == "John") > $p2 : Person(name == "Paul") > then > list.add($p1.getAge()); > list.add($p2.getAge()); > modify($p1) { setAge($p1.getAge()+1) } > list.add($p1.getAge()); > list.add($p2.getAge()); > modify($p2) { setAge($p2.getAge()+5) } > list.add($p1.getAge()); > list.add($p2.getAge()); > end > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5271) RHS statements ordering changes with modify block in executable model

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5271: ----------------------------------------- Summary: RHS statements ordering changes with modify block in executable model Key: DROOLS-5271 URL: https://issues.redhat.com/browse/DROOLS-5271 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.36.0.Final Reporter: Toshiya Kobayashi Assignee: Luca Molteni The order of statements in RHS changes with executable model when modify block is involved. The below rule can tell the difference with standard-drl. {noformat} import org.drools.modelcompiler.domain.Person;global java.util.List list; rule R when $p1 : Person(name == "John") $p2 : Person(name == "Paul") then list.add($p1.getAge()); list.add($p2.getAge()); modify($p1) { setAge($p1.getAge()+1) } list.add($p1.getAge()); list.add($p2.getAge()); modify($p2) { setAge($p2.getAge()+5) } list.add($p1.getAge()); list.add($p2.getAge()); end {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5271) RHS statements ordering changes with modify block in executable model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5271?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-5271: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Luca Molteni) > RHS statements ordering changes with modify block in executable model > --------------------------------------------------------------------- > > Key: DROOLS-5271 > URL: https://issues.redhat.com/browse/DROOLS-5271 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.36.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > The order of statements in RHS changes with executable model when modify block is involved. The below rule can tell the difference with standard-drl. > {noformat} > import org.drools.modelcompiler.domain.Person;global java.util.List list; > rule R when > $p1 : Person(name == "John") > $p2 : Person(name == "Paul") > then > list.add($p1.getAge()); > list.add($p2.getAge()); > modify($p1) { setAge($p1.getAge()+1) } > list.add($p1.getAge()); > list.add($p2.getAge()); > modify($p2) { setAge($p2.getAge()+5) } > list.add($p1.getAge()); > list.add($p2.getAge()); > end > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4915) Tighten up the dependency tree of subsystem-test

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4915?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4915: ------------------------------------------ [~kabirkhan] Yes, it was possible to tighten up the MP subsystem deps: https://github.com/wildfly/wildfly/pull/13206 > Tighten up the dependency tree of subsystem-test > ------------------------------------------------ > > Key: WFCORE-4915 > URL: https://issues.redhat.com/browse/WFCORE-4915 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 12.0.0.Beta2 > > > In general I'd like to tighten (aka eliminate) up the use of transitive dependencies when various WildFly and WildFly Core maven modules depend on each other. Things should be explicit so unwanted coupling cannot creep in. > The subsystem-test module is important in this regard as pretty much all extension modules depend on it's pom. So I want it and its children and its direct dependencies to only depend on other wf core modules directly, no transitive deps allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-13404) Upgrade Hibernate ORM from 5.3.16 to 5.3.17

by Gail Badner (Jira)

Gail Badner created WFLY-13404: ---------------------------------- Summary: Upgrade Hibernate ORM from 5.3.16 to 5.3.17 Key: WFLY-13404 URL: https://issues.redhat.com/browse/WFLY-13404 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Gail Badner Fix For: 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12134) Add org.infinispan:infinispan-multimap, org.infinispan:infinispan-clustered-counter, org.infinispan:infinispan-clustered-lock modules

by Sergey Aganin (Jira)

[ https://issues.redhat.com/browse/WFLY-12134?page=com.atlassian.jira.plugi... ] Sergey Aganin commented on WFLY-12134: -------------------------------------- [~jputney] I made an example for using a LockService for Wildfly. [Example JGroups LockService for Wildfly|https://github.com/IamUndef/wildfly-jgroups-lock] > Add org.infinispan:infinispan-multimap, org.infinispan:infinispan-clustered-counter, org.infinispan:infinispan-clustered-lock modules > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12134 > URL: https://issues.redhat.com/browse/WFLY-12134 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 17.0.0.Beta1 > Reporter: Sergey Aganin > Assignee: Paul Ferraro > Priority: Major > > Please add the modules such that users can use the new features of Infinispan. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-907) UI Automations - Fix random failures on master

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-907?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan commented on SWSQE-907: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/282 > UI Automations - Fix random failures on master > ---------------------------------------------- > > Key: SWSQE-907 > URL: https://issues.redhat.com/browse/SWSQE-907 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4395) JDR collect free disk space

by Dennis Reed (Jira)

[ https://issues.redhat.com/browse/WFLY-4395?page=com.atlassian.jira.plugin... ] Dennis Reed commented on WFLY-4395: ----------------------------------- Current behavior: JDR does not contain data about free disk space. Desired behavior: JDR collects and reports data about free disk space in the server. > JDR collect free disk space > --------------------------- > > Key: WFLY-4395 > URL: https://issues.redhat.com/browse/WFLY-4395 > Project: WildFly > Issue Type: Enhancement > Components: JDR > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Major > > JDR collect free disk space as server can throw errors when there is no free space. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4905) Provide common capability for Remoting connectors

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4905?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved WFCORE-4905. -------------------------------------- Fix Version/s: 11.0.1.Final (was: 12.0.0.Beta2) Resolution: Rejected Changes not required in 11.0.x > Provide common capability for Remoting connectors > ------------------------------------------------- > > Key: WFCORE-4905 > URL: https://issues.redhat.com/browse/WFCORE-4905 > Project: WildFly Core > Issue Type: Bug > Components: Remoting > Affects Versions: 11.0.0.Final > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Priority: Major > Fix For: 11.0.1.Final > > > The EJB3 subsystem has an element <remote/> which performs a few different functions relating to external clients accessing EJBs on the server: > * sets up a Remoting connector service so that external clients may connect to the server using EJB / Remoting or EJB / HTTP Upgrade / Remoting > * sets up client mappings entries for those remote clients which are used in topology updates to allow the client to find the server's connectors > The Remoting subsystem has two connector types which may be supplied to the <remote connector-ref/> attribute. <connector name="remoting-connector"/> represents a Remoting endpoint and <http-connector name="http-connector"/> represents an Undertow listener which may be used with HTTP Upgrade. > At present, in the Remoting subsystem, these connectors have two separately defined capabilities: > // for <connector/> > private static final String CONNECTOR_CAPABILITY_NAME ="org.wildfly.remoting.connector"; > static final RuntimeCapability<Void> CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(CONNECTOR_CAPABILITY_NAME, true).build(); > // for <http-connector/> > private static final String HTTP_CONNECTOR_CAPABILITY_NAME = "org.wildfly.remoting.http-connector"; > static final RuntimeCapability<Void> HTTP_CONNECTOR_CAPABILITY = RuntimeCapability.Builder.of(HTTP_CONNECTOR_CAPABILITY_NAME, true).build(); > The proposal here is to allow referencing both connectors using a single capability base name, "org.wildfly.remoting.connector" to simplify specification of the capabilities which the <remote/> element needs (i.e. it may depend on one or the other). These are both dynamically named capabilities, so their names will vary based on the name of the management resource instance they represent. Because capability names are considered public API, the existing capability name for org.wildfly.remoting.http-connector cannot be removed to further simplify. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5261) Move shared "drools-model-related" classes to common module

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5261?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5261. ------------------------------------ > Move shared "drools-model-related" classes to common module > ----------------------------------------------------------- > > Key: DROOLS-5261 > URL: https://issues.redhat.com/browse/DROOLS-5261 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Most KiePMML ASTFactories created inside TreeModel module are actually to be shared with other modules (e.g. Scorecard). This task is about moving them (and related tests) to kie-pmml-models-drools-common -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 April 2020