December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4870) Materialize consequences using Drools

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4870?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4870: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > Materialize consequences using Drools > ------------------------------------- > > Key: DROOLS-4870 > URL: https://issues.redhat.com/browse/DROOLS-4870 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently consequences using Drools are not materialized (extracted in a different lambda) because they are capturing, as they use the relative bitmask instance. > We should find a way to pass the bitmask instance to the consequence so that we can materialize them. > This means we should probably not change only the compiler, but also the interpreter of the DSL -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4600) Embedded Camel endpoints don't work with executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4600?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4600: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 50-52 (from Dec 9)) > Embedded Camel endpoints don't work with executable model > --------------------------------------------------------- > > Key: DROOLS-4600 > URL: https://issues.redhat.com/browse/DROOLS-4600 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.27.0.Final > Reporter: Tibor Zimanyi > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > When having and embedded Camel endpoint it DRL, it doesn't work with executable model. Reproducer can be found here [1]. For the test to reproduce the issue, it is needed to use executable model project in the buildAll() call here [2]. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/5f95febee0c081310... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-camel/... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2425) RELAY2: new commands to print topology, site-masters, sites etc

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2425?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2425. ---------------------------- Resolution: Done > RELAY2: new commands to print topology, site-masters, sites etc > --------------------------------------------------------------- > > Key: JGRP-2425 > URL: https://issues.redhat.com/browse/JGRP-2425 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.9 > > > Add a bunch of utility commands, e.g. (from {{RelayDemo}}): > {noformat} > commands: > help > mbrs: prints the local members > site-masters (sm): prints the site masters of this site > sites: prints the configured sites > topo: prints the topology (site masters and local members of all sites) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12891) JAXB Unmarshaller tries to instantiate abstract class ignoring xsi:type if it is a list element

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12891?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFLY-12891: ------------------------------------- I'm reopening this because it's not fixed in WildFly until the component upgrade fixing it is done. > JAXB Unmarshaller tries to instantiate abstract class ignoring xsi:type if it is a list element > ----------------------------------------------------------------------------------------------- > > Key: WFLY-12891 > URL: https://issues.redhat.com/browse/WFLY-12891 > Project: WildFly > Issue Type: Bug > Reporter: Lin Gao > Assignee: Lin Gao > Priority: Major > Labels: downstream_dependency > > Upstream Issue: https://github.com/eclipse-ee4j/jaxb-ri/issues/1135 > Upstream PR: https://github.com/eclipse-ee4j/jaxb-ri/pull/1294 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-12913: --------------------------------------- Assignee: (was: Scott Marlow) > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Priority: Major > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12913: ------------------------------------ Priority: Minor (was: Major) > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Priority: Minor > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12913: ------------------------------------ Description: The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: {code} <module name="com.github.relaxng" export="true" /> <module name="com.sun.istack" export="true" /> <module name="com.sun.xml.txw2" export="true" /> <module name="com.sun.xsom" export="true" /> {code} Task is to: 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. 3) Assuming no positive responses, make the artifacts from the above four direct artifacts of the com.sun.xml.bind module, > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Major > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four direct artifacts of the com.sun.xml.bind module, -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12913: ------------------------------------ Description: The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: {code} <module name="com.github.relaxng" export="true" /> <module name="com.sun.istack" export="true" /> <module name="com.sun.xml.txw2" export="true" /> <module name="com.sun.xsom" export="true" /> {code} Task is to: 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. was: The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: {code} <module name="com.github.relaxng" export="true" /> <module name="com.sun.istack" export="true" /> <module name="com.sun.xml.txw2" export="true" /> <module name="com.sun.xsom" export="true" /> {code} Task is to: 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. 3) Assuming no positive responses, make the artifacts from the above four direct artifacts of the com.sun.xml.bind module, > Rationalize com.sum.xml.bind module dependencies > ------------------------------------------------ > > Key: WFLY-12913 > URL: https://issues.redhat.com/browse/WFLY-12913 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate, REST, Web Services > Reporter: Brian Stansberry > Assignee: Scott Marlow > Priority: Major > > The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents: > {code} > <module name="com.github.relaxng" export="true" /> > <module name="com.sun.istack" export="true" /> > <module name="com.sun.xml.txw2" export="true" /> > <module name="com.sun.xsom" export="true" /> > {code} > Task is to: > 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules. > 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules. > 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12913: --------------------------------------- Summary: Rationalize com.sum.xml.bind module dependencies Key: WFLY-12913 URL: https://issues.redhat.com/browse/WFLY-12913 Project: WildFly Issue Type: Task Components: JPA / Hibernate, REST, Web Services Reporter: Brian Stansberry Assignee: Scott Marlow -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-218) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFWIP-218?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFWIP-218: ---------------------------------------- [~simkam] [~ochaloup] Should this be moved to another tracker, i.e. WFLY? It sounds like it is not about an unmerged feature. > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFWIP-218 > URL: https://issues.redhat.com/browse/WFWIP-218 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > this follows up on WFWIP-206 > While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful > Scenario: > *ejb client* (app tx-client, pod tx-client-0): > * EJB business method > ** lookup remote EJB > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > ** call remote EJB > *ejb server* (app tx-server, pod tx-server-0): > * EJB business method > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > *testTxStatelessServerSecondCommitThrowRmFail* > ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}} > Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client and transactions on client aren't commited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 December 2019