August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-215) Jakarta Concurrency API Manifest Setup

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-215?page=com.atlassian.jira.plugin.s... ] Eduardo Martins commented on JBEE-215: -------------------------------------- PR: https://github.com/jboss/jboss-jakarta-concurrency-api/pull/1 > Jakarta Concurrency API Manifest Setup > -------------------------------------- > > Key: JBEE-215 > URL: https://issues.jboss.org/browse/JBEE-215 > Project: JBoss Enterprise Spec APIs > Issue Type: Enhancement > Components: jboss-javaee-concurrency-api > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > The MANIFEST file for the Jakarta Concurrency API fork should be configured similar to what was done to Java EE Concurrency API fork, see https://github.com/jboss/jboss-javaee-concurrency-api_spec/blob/master/po... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-217) Add LICENSE to Jakarta API artifact

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-217: ------------------------------------ Summary: Add LICENSE to Jakarta API artifact Key: JBEE-217 URL: https://issues.jboss.org/browse/JBEE-217 Project: JBoss Enterprise Spec APIs Issue Type: Enhancement Components: jboss-javaee-concurrency-api Reporter: Eduardo Martins Assignee: Eduardo Martins The root LICENSE.md file should be included in the built artifact. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-216) Cleanup Jakarta Concurrency API maven plugin management and executions

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-216: ------------------------------------ Summary: Cleanup Jakarta Concurrency API maven plugin management and executions Key: JBEE-216 URL: https://issues.jboss.org/browse/JBEE-216 Project: JBoss Enterprise Spec APIs Issue Type: Enhancement Components: jboss-javaee-concurrency-api Reporter: Eduardo Martins Assignee: Eduardo Martins There are several maven plugins not needed to be managed and/or executed when building Jakarta Concurrency, which adds unnecessary dependencies and/or conflicts with JBoss Parent definitions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBEE-215) Jakarta Concurrency API Manifest Setup

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-215: ------------------------------------ Summary: Jakarta Concurrency API Manifest Setup Key: JBEE-215 URL: https://issues.jboss.org/browse/JBEE-215 Project: JBoss Enterprise Spec APIs Issue Type: Enhancement Components: jboss-javaee-concurrency-api Reporter: Eduardo Martins Assignee: Eduardo Martins The MANIFEST file for the Jakarta Concurrency API fork should be configured similar to what was done to Java EE Concurrency API fork, see https://github.com/jboss/jboss-javaee-concurrency-api_spec/blob/master/po... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4454) NullPointerException at org.drools.core.phreak.SegmentUtilities.createChildSegments with a removed rule in updateToVersion

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4454?page=com.atlassian.jira.plugi... ] Martin Weiler moved RHDM-1067 to DROOLS-4454: --------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4454 (was: RHDM-1067) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: core engine (was: BRE) Affects Version/s: 7.25.0.Final (was: 7.4.1.GA) QE Status: NEW > NullPointerException at org.drools.core.phreak.SegmentUtilities.createChildSegments with a removed rule in updateToVersion > -------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4454 > URL: https://issues.jboss.org/browse/DROOLS-4454 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.25.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > > After an updateToVersion where a rule is removed from the KieBase, > fireAllRules fails with the exception below. > Note: This happens with versions 6.4.0.Final-redhat-6 and later > (including latest master) > The following commit seems to be causing the NPE: > https://issues.jboss.org/browse/DROOLS-1147 > https://github.com/kiegroup/drools/commit/8897a8dcccce10a93803d7073ecf499... > {noformat} > java.lang.NullPointerException > at org.drools.core.phreak.SegmentUtilities.createChildSegments(SegmentUtilities.java:305) > at org.drools.core.reteoo.LeftInputAdapterNode.doInsertObject(LeftInputAdapterNode.java:185) > at org.drools.core.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:169) > at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:63) > at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304) > at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:120) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:77) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2044) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1334) > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1333) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1324) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1305) > at CreateChildSegmentNpeTest.fireAllRules(CreateChildSegmentNpeTest.java:91) > at CreateChildSegmentNpeTest.reproducer(CreateChildSegmentNpeTest.java:126) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by Matt Drees (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Matt Drees edited comment on WFLY-2859 at 8/21/19 5:19 PM: ----------------------------------------------------------- Ah, that makes sense. Yeah, a RESTEasy upgraded is indeed required. The fix should be in 3.9, whenever it is released. (probably as 3.9.0.Final) was (Author: matt.drees): Ah, that makes sense. Yeah, a RESTEasy upgraded is indeed required. > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by Matt Drees (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Matt Drees commented on WFLY-2859: ---------------------------------- Ah, that makes sense. Yeah, a RESTEasy upgraded is indeed required. > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] James Perkins reopened WFLY-2859: --------------------------------- Assignee: Ronald Sigal (was: Stuart Douglas) > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2859: ------------------------------------- [~matt.drees] sorry that's my bad. I missed the part II JIRA. I'll reopen this as it seems like it shouldn't be resolved until RESTEasy is upgraded. > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Stuart Douglas > Priority: Major > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4453) Test Scenario: empty values in collection should be always skipped

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4453?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4453: --------------------------------------- [~juliaaano] FYI Here is the bug related to your reproducer > Test Scenario: empty values in collection should be always skipped > ------------------------------------------------------------------ > > Key: DROOLS-4453 > URL: https://issues.jboss.org/browse/DROOLS-4453 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > See this project as reproducer > https://github.com/juliaaano/temp -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 2019