July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10775) Upgrade to Apache CXF 3.2.5-jbossorg-1

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10775?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-10775: ----------------------------------- Fix Version/s: 14.0.0.CR1 > Upgrade to Apache CXF 3.2.5-jbossorg-1 > -------------------------------------- > > Key: WFLY-10775 > URL: https://issues.jboss.org/browse/WFLY-10775 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 14.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10775) Upgrade to Apache CXF 3.2.5-jbossorg-1

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-10775: -------------------------------------- Summary: Upgrade to Apache CXF 3.2.5-jbossorg-1 Key: WFLY-10775 URL: https://issues.jboss.org/browse/WFLY-10775 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Alessio Soldano -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2792: ---------------------------------------- [~uxdlc] [~tirelli] I need your thoughts on the data-type editor used for input/output data-types of boxed expression elements. I've attached a document showing what we currently have (2 rows in the header, 1 for name and 1 for data-type) and a single editor for the different _core_ properties (remember the "Properties Panel" will show all properties for the DMN element). Another option would be to support different editors for different components within a cell/header and each is shown "in grid" (at the moment the framework only supports one editor per cell/header). Multiple rows in the header for the different _core_ properties is OK for {{LiteralExpression}} and {{DecisionTable}} but does not work for {{ContextEntry}}. > [DMN Designer] Data-types: Grid: LiteralExpression > -------------------------------------------------- > > Key: DROOLS-2792 > URL: https://issues.jboss.org/browse/DROOLS-2792 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2792.odt > > > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3985) The DeploymentOverlayTestCase uses the incorrect suite reference

by James Perkins (JIRA)

James Perkins created WFCORE-3985: ------------------------------------- Summary: The DeploymentOverlayTestCase uses the incorrect suite reference Key: WFCORE-3985 URL: https://issues.jboss.org/browse/WFCORE-3985 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: James Perkins Assignee: James Perkins The {{DeploymentOverlayTestCase}} is part of the {{CLITestSuite}} however when starting/stopping the {{DomainTestSupport}} it references the {{DomainTestSuite}} which attempts to start a new set of servers. The test should use the {{CLITestSuite}} static methods for starting/stopping the {{DomainTestSupport}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2792: ----------------------------------- Attachment: DROOLS-2792.odt > [DMN Designer] Data-types: Grid: LiteralExpression > -------------------------------------------------- > > Key: DROOLS-2792 > URL: https://issues.jboss.org/browse/DROOLS-2792 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2792.odt > > > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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 updated WFCORE-3984: -------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3406 > 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)

6 years, 5 months

1
0
0 / 0

[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)

6 years, 5 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)

6 years, 5 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)

6 years, 5 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)

6 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2018