July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10754) NullPointerException using Stateless with configured interceptors

by Luca Stancapiano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10754?page=com.atlassian.jira.plugin... ] Luca Stancapiano commented on WFLY-10754: ----------------------------------------- the test works. I started also the other test cases and all tests continue to work, so for me it's ok. Only I renamed the CombinedInterceptorsOnEJBBeanTest to CombinedInterceptorsOnEJBBeanTestCase as for the other test cases. You can find the update in [my branch|https://github.com/flashboss/wildfly/tree/wfly10754] > NullPointerException using Stateless with configured interceptors > ----------------------------------------------------------------- > > Key: WFLY-10754 > URL: https://issues.jboss.org/browse/WFLY-10754 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 13.0.0.Final > Environment: WildFly 12.0.0.Final and newer > Reporter: Luca Stancapiano > Assignee: Matej Novotny > Priority: Minor > > I report a strange behavior on WildFly 13 when configuring interceptors within stateless. Below I describe the scenario: > Here a simple interceptor: > {code:java} > package it.vige.injection.interceptors; > import javax.interceptor.AroundInvoke; > import javax.interceptor.Interceptor; > import javax.interceptor.InvocationContext; > @Interceptor > public class OKInterceptor { > @AroundInvoke > public Object aroundInvoke(InvocationContext ic) throws Exception { > return ic.proceed(); > } > } > {code} > Here an annotation used as interceptor binding: > {code:java} > package it.vige.injection.interceptors; > import static java.lang.annotation.ElementType.CONSTRUCTOR; > import static java.lang.annotation.ElementType.METHOD; > import static java.lang.annotation.ElementType.TYPE; > import static java.lang.annotation.RetentionPolicy.RUNTIME; > import java.lang.annotation.Retention; > import java.lang.annotation.Target; > import javax.interceptor.InterceptorBinding; > @Retention(RUNTIME) > @Target({ METHOD, TYPE, CONSTRUCTOR }) > @InterceptorBinding > public @interface NotOK { > } > {code} > Here an interceptor annotated with the interceptor binding: > {code:java} > package it.vige.injection.interceptors; > import javax.interceptor.AroundInvoke; > import javax.interceptor.Interceptor; > import javax.interceptor.InvocationContext; > @Interceptor > @NotOK > public class NotOKInterceptor { > @AroundInvoke > public Object aroundInvoke(InvocationContext ic) throws Exception { > return ic.proceed(); > } > } > {code} > Here the stateless service configured with both the interceptors: > {code:java} > package it.vige.injection.interceptors; > import javax.ejb.Stateless; > import javax.interceptor.Interceptors; > @Stateless > public class SimpleService { > @Interceptors({ OKInterceptor.class }) > public void ok() { > } > @NotOK > public void notOk() { > } > } > {code} > This service must have two methods, one attached to the simple interceptor and the other attached to the interceptor binding. > Here the beans.xml configuration: > {code:java} > <beans xmlns="http://xmlns.jcp.org/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee > http://xmlns.jcp.org/xml/ns/javaee/beans_2_0.xsd" > version="2.0" bean-discovery-mode="all"> > <interceptors> > <class>it.vige.injection.interceptors.OKInterceptor</class> > <class>it.vige.injection.interceptors.NotOKInterceptor</class> > </interceptors> > </beans> > {code} > And in the end the client who call the service: > {code:java} > .... > @Inject > private SimpleService simpleService; > ... > // this call works: > simpleService.ok(); > // this call starts a NullPointerException: > simpleService.notOk(); > ... > {code} > when I try to call the notOk method I get this exception: > {code:java} > javax.ejb.EJBException: java.lang.NullPointerException > at deployment.test.war//it.vige.injection.test.InterceptorsTestCase.testNotOk(InterceptorsTestCase.java:52) > Caused by: java.lang.NullPointerException > at deployment.test.war//it.vige.injection.test.InterceptorsTestCase.testNotOk(InterceptorsTestCase.java:52) > {code} > The same thing was tested on WildFly 11.0.0.Final and it was ok. > If on WildFfly 13.0.0.Final I remove the @Stateless annotation from the service it works -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3984) WildFly Core TS failures on Java 11 (--add-modules java.se)

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3984?page=com.atlassian.jira.plugi... ] Rostislav Svoboda moved WFLY-10774 to WFCORE-3984: -------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3984 (was: WFLY-10774) Component/s: Test Suite (was: Test Suite) > WildFly Core TS failures on Java 11 (--add-modules java.se) > ------------------------------------------------------------ > > Key: WFCORE-3984 > URL: https://issues.jboss.org/browse/WFCORE-3984 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > > WildFly Core TS failures on Java 11 > Majority of fails coul go away by adding --add-modules java.se into modular.jdk.args in jdk9 module -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10774) WildFly Core TS failures on Java 11 (--add-modules java.se)

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-10774: ---------------------------------------- Summary: WildFly Core TS failures on Java 11 (--add-modules java.se) Key: WFLY-10774 URL: https://issues.jboss.org/browse/WFLY-10774 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda WildFly Core TS failures on Java 11 Majority of fails coul go away by adding --add-modules java.se into modular.jdk.args in jdk9 module -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9707) Remove JASPI module

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9707?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9707: ----------------------------------- Fix Version/s: 14.0.0.CR1 > Remove JASPI module > ------------------- > > Key: WFLY-9707 > URL: https://issues.jboss.org/browse/WFLY-9707 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2810) Kie-dmn OSGI feature can not be installed

by Jiri Petrlik (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2810?page=com.atlassian.jira.plugi... ] Jiri Petrlik edited comment on DROOLS-2810 at 7/31/18 10:05 AM: ---------------------------------------------------------------- Problem was caused by changes in kie dmn core dependencies [1]. Fixed by adding model to drools-module feature and OSGIfing module and its dependencies. Unfortunately changes are in three PRs which need to be merged simultaneously. [1] https://github.com/kiegroup/drools/commit/0efe87b4166072eaa9af4076e53471c... was (Author: jpetrlik): Problem was caused by changes in drools core dependencies [1]. Fixed by adding model to drools-module feature and OSGIfing module and its dependencies. Unfortunately changes are in three PRs which need to be merged simultaneously. [1] https://github.com/kiegroup/drools/commit/0efe87b4166072eaa9af4076e53471c... > Kie-dmn OSGI feature can not be installed > ----------------------------------------- > > Key: DROOLS-2810 > URL: https://issues.jboss.org/browse/DROOLS-2810 > Project: Drools > Issue Type: Bug > Components: integration > Reporter: Jiri Petrlik > Assignee: Jiri Petrlik > Fix For: 7.10.0.Final > > > It is not possible to install kie-dmn OSGI feature. Installation fails with following exception: > Unable to resolve org.kie.dmn.core/7.10.0.201807310901: missing requirement [org.kie.dmn.core/7.10.0.201807310901] osgi.wiring.package; filter:="(osgi.wiring.package=org.drools.model)" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3983) Update the WildFly Elytron Subsystem to use the new MSC Service API

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3983: ---------------------------------------- Summary: Update the WildFly Elytron Subsystem to use the new MSC Service API Key: WFCORE-3983 URL: https://issues.jboss.org/browse/WFCORE-3983 Project: WildFly Core Issue Type: Task Components: Security Reporter: Darran Lofthouse At some point we want to consider breaking the subsystem into smaller chunks to allow a more selective subset of functionality to be selected - before we do that it would be good to clean up the general approach in the subsystem. We have trivial resources and services within the subsystem but the new MSC APIs may simpify a lot of this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-363) Fix failing UI automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-363?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-363. ---------------------------------- Resolution: Done PR merged https://github.com/Kiali-QE/kiali-qe-python/pull/63 > Fix failing UI automation tests > ------------------------------- > > Key: SWSQE-363 > URL: https://issues.jboss.org/browse/SWSQE-363 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10471) Rework mod_cluster load provider into proper resources

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10471?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10471: ---------------------------------- Affects Version/s: 13.0.0.Final > Rework mod_cluster load provider into proper resources > ------------------------------------------------------ > > Key: WFLY-10471 > URL: https://issues.jboss.org/browse/WFLY-10471 > Project: WildFly > Issue Type: Task > Components: mod_cluster > Affects Versions: 13.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > Follow up on WFLY-8364. It would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10440) Upgrade mod_cluster to 1.4.0.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10440?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10440: ---------------------------------- Affects Version/s: 13.0.0.Final > Upgrade mod_cluster to 1.4.0.Final > ---------------------------------- > > Key: WFLY-10440 > URL: https://issues.jboss.org/browse/WFLY-10440 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tag https://github.com/modcluster/mod_cluster/tree/1.4.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10440) Upgrade mod_cluster to 1.4.0.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10440?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10440: ---------------------------------- Fix Version/s: (was: 14.0.0.CR1) > Upgrade mod_cluster to 1.4.0.Final > ---------------------------------- > > Key: WFLY-10440 > URL: https://issues.jboss.org/browse/WFLY-10440 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tag https://github.com/modcluster/mod_cluster/tree/1.4.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2018