May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1562) NPE when creating KieModuleMetaData with wrong release id

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1562?page=com.atlassian.jira.plugi... ] Maciej Swiderski commented on DROOLS-1562: ------------------------------------------ [~mfusco] there seems to be two issues: - one in KieModuleMetaData as illustrated in the attached stack trace - another in updateToVersion method of KieContainerImpl that leads to following NPE: {code} java.lang.NullPointerException: null at org.drools.compiler.kie.util.ChangeSetBuilder.build(ChangeSetBuilder.java:57) ~[drools-compiler-7.1.0-20170508.233901-66.jar:7.1.0-SNAPSHOT] at org.drools.compiler.kie.builder.impl.KieContainerImpl.update(KieContainerImpl.java:236) ~[drools-compiler-7.1.0-20170508.233901-66.jar:7.1.0-SNAPSHOT] at org.drools.compiler.kie.builder.impl.KieContainerImpl.updateToVersion(KieContainerImpl.java:202) ~[drools-compiler-7.1.0-20170508.233901-66.jar:7.1.0-SNAPSHOT] {code} > NPE when creating KieModuleMetaData with wrong release id > --------------------------------------------------------- > > Key: DROOLS-1562 > URL: https://issues.jboss.org/browse/DROOLS-1562 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.CR3 > Reporter: Karel Suta > Assignee: Mario Fusco > Labels: reported-by-qe > Attachments: stacktrace.txt > > > If user tries to create new KieModuleMetaData using KieModuleMetaData.Factory.newKieModuleMetaData() with not existing release id then NPE is thrown, see stacktrace in attachment. > This error can be simulated on Kie server. See PR with reproducer [1]. > [1] https://github.com/kiegroup/droolsjbpm-integration/pull/950 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-138) Allow a URI for the Elytron configuration to be passed to environment when establishing a connection

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/REMJMX-138?page=com.atlassian.jira.plugin... ] James Perkins updated REMJMX-138: --------------------------------- Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/29 > Allow a URI for the Elytron configuration to be passed to environment when establishing a connection > ---------------------------------------------------------------------------------------------------- > > Key: REMJMX-138 > URL: https://issues.jboss.org/browse/REMJMX-138 > Project: Remoting JMX > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.url}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one. > This is more of a nice to have for clients so they do not need to be aware of using Elytron directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-138) Allow a URI for the Elytron configuration to be passed to environment when establishing a connection

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/REMJMX-138?page=com.atlassian.jira.plugin... ] James Perkins updated REMJMX-138: --------------------------------- Description: Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.url}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one. This is more of a nice to have for clients so they do not need to be aware of using Elytron directly. was: Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.uri}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one. This is more of a nice to have for clients so they do not need to be aware of using Elytron directly. > Allow a URI for the Elytron configuration to be passed to environment when establishing a connection > ---------------------------------------------------------------------------------------------------- > > Key: REMJMX-138 > URL: https://issues.jboss.org/browse/REMJMX-138 > Project: Remoting JMX > Issue Type: Enhancement > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.url}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one. > This is more of a nice to have for clients so they do not need to be aware of using Elytron directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-138) Allow a URI for the Elytron configuration to be passed to environment when establishing a connection

by James Perkins (JIRA)

James Perkins created REMJMX-138: ------------------------------------ Summary: Allow a URI for the Elytron configuration to be passed to environment when establishing a connection Key: REMJMX-138 URL: https://issues.jboss.org/browse/REMJMX-138 Project: Remoting JMX Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Priority: Minor Currently the current Elytron {{AuthenticationContext}} is captured when establishing a connection. It would be beneficial for clients to be able to pass a property, likely {{wildfly.config.uri}} to be consistent with the system property, to the path of the configuration file and have the file parsed by Elytron. The {{AuthenticationContext}} parsed from the configuration file would be used instead of the currently captured one. This is more of a nice to have for clients so they do not need to be aware of using Elytron directly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-20) Misc. code improvements suggested by static analysis

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-20?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-20: ---------------------------- Component/s: (was: infrastructure) > Misc. code improvements suggested by static analysis > ----------------------------------------------------- > > Key: AG-20 > URL: https://issues.jboss.org/browse/AG-20 > Project: Agroal > Issue Type: Task > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-21) Allow connections without transaction in JTA environments

by Luis Barreiro (JIRA)

Luis Barreiro created AG-21: ------------------------------- Summary: Allow connections without transaction in JTA environments Key: AG-21 URL: https://issues.jboss.org/browse/AG-21 Project: Agroal Issue Type: Task Components: narayana Affects Versions: 0.1 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-15) Implement a benchmark

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-15?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-15: ---------------------------- Affects Version/s: 0.1 (was: 0,1) > Implement a benchmark > --------------------- > > Key: AG-15 > URL: https://issues.jboss.org/browse/AG-15 > Project: Agroal > Issue Type: Task > Components: benchmark > Affects Versions: 0.1 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.2 > > > The goal is to provide reliable data to compare the performance of the different features. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-20) Misc. code improvements suggested by static analysis

by Luis Barreiro (JIRA)

Luis Barreiro created AG-20: ------------------------------- Summary: Misc. code improvements suggested by static analysis Key: AG-20 URL: https://issues.jboss.org/browse/AG-20 Project: Agroal Issue Type: Task Components: infrastructure Reporter: Luis Barreiro Assignee: Luis Barreiro Priority: Minor Fix For: 0.2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AG-19) Implement integration with JBoss Threads for interrupt protection

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-19?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-19. ----------------------------- Fix Version/s: 0.2 Resolution: Done > Implement integration with JBoss Threads for interrupt protection > ----------------------------------------------------------------- > > Key: AG-19 > URL: https://issues.jboss.org/browse/AG-19 > Project: Agroal > Issue Type: Task > Components: jboss-threads > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1152) Rework security Provider behaviour

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1152?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1152: ---------------------------------- Fix Version/s: 1.1.0.Beta43 > Rework security Provider behaviour > ---------------------------------- > > Key: ELY-1152 > URL: https://issues.jboss.org/browse/ELY-1152 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta43 > > > Everything that makes use of providers should be using a Supplier<Provider[]> which exists as a result of parsing the configuration. > Our default behaviour should likely be a combination of globally defined providers, and service loader discovered providers. Config then is more likely to be about disabling one or both rather than enabling. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017