May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBAS-8818) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

[ https://issues.jboss.org/browse/JBAS-8818?page=com.atlassian.jira.plugin.... ] Archimedes Trajano edited comment on JBAS-8818 at 5/8/17 7:38 PM: ------------------------------------------------------------------ This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. If you want to see a project that uses CDI extensively https://github.com/trajano/jee/tree/for-JBAS-8818 was (Author: archimedes.trajano): This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. > CDI injection not working in WebListeners > ----------------------------------------- > > Key: JBAS-8818 > URL: https://issues.jboss.org/browse/JBAS-8818 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Weld/CDI > Affects Versions: 6.0.0.Final > Reporter: Nicklas Karlsson > Assignee: Marius Bogoevici > > CDI injection is not performed for WebListeners, e.g. > @WebListener > public class BugListener implements HttpSessionListener > { > @Inject > BeanManager beanManager; > ... > } > Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBAS-8818) CDI injection not working in WebListeners

by Archimedes Trajano (JIRA)

[ https://issues.jboss.org/browse/JBAS-8818?page=com.atlassian.jira.plugin.... ] Archimedes Trajano commented on JBAS-8818: ------------------------------------------ This still applies to WildFly 10. I am attempting to port my application which works properly on WebSphere Liberty and WebSphere 9.0 to WildFly and fixed most of the weird nuances such as... JPQL not supporting `NOT p.cancelled` and having to use p.cancelled = false` Using an undocumented (at least not in https://docs.jboss.org/author/display/AS71/Deployment+Descriptors+used+In...) jboss-app descriptor to set up the reference to the data source and adding a lookup name to it which I didn't need to do in WebSphere. Changing the scope of JPA Converters and using an explicit InitialContext lookup for SessionContext since @Resource didn't work in JPA Event Listeners. This problem with EJBs not being injected in WebListener also applies to WebService, WebServlet and JAX-RS as well. > CDI injection not working in WebListeners > ----------------------------------------- > > Key: JBAS-8818 > URL: https://issues.jboss.org/browse/JBAS-8818 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Components: Weld/CDI > Affects Versions: 6.0.0.Final > Reporter: Nicklas Karlsson > Assignee: Marius Bogoevici > > CDI injection is not performed for WebListeners, e.g. > @WebListener > public class BugListener implements HttpSessionListener > { > @Inject > BeanManager beanManager; > ... > } > Will have beanManager==null when the methods are hit -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2746) Move elytron management security tests from full to core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2746?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-2746: ------------------------------ Description: Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 There are a number of aspects to this, for which I'll create subtasks. Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. -org.jboss.as.test.integration.security.perimeter.* [2]- -org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase- -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- org.jboss.as.test.integration.security.credentialreference [2] [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. [2] Currently using Arquillian. was: Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 There are a number of aspects to this, for which I'll create subtasks. Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. org.jboss.as.test.integration.security.perimeter.* [2] org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- org.jboss.as.test.integration.security.credentialreference [2] (This is using h2 / datasources, so not moving). [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. [2] Currently using Arquillian. > Move elytron management security tests from full to core > -------------------------------------------------------- > > Key: WFCORE-2746 > URL: https://issues.jboss.org/browse/WFCORE-2746 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security, Test Suite > Reporter: Brian Stansberry > > Since until recently the elytron subsystem wasn't part of the core feature pack, a lot of integration tests of its use ended up in the WildFly full testsuite instead of in core. This task is to get tests that are only testing core functionality moved into the core testsuite. Because that's the right thing to do, but also because it's useful in practice by eliminating a cause for messy coordinated changes to core and full such that code changes in core can be tested. > Corresponding Wildfly JIRA: https://issues.jboss.org/browse/WFLY-8723 > There are a number of aspects to this, for which I'll create subtasks. > Following is an initial list of tests that should be moved. *This is meant to be a living list, with things added as they are noticed.* So anyone should feel free to edit this JIRA description to add things to the list. > -org.jboss.as.test.integration.security.perimeter.* [2]- > -org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase- > -org.jboss.as.test.integration.domain.AbstractSlaveHCAuthenticationTestCase and subclasses.[1]- > org.jboss.as.test.integration.security.credentialreference [2] > [1] One subclass of this is not related to elytron but should be moved to core too. I haven't looked closely but it uses vault, which may be why it is in full. But we can use vault in the core testsuite now. > [2] Currently using Arquillian. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2774) Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2774?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-2774: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2378/commits/6bc44155f7a3390... > Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2774 > URL: https://issues.jboss.org/browse/WFCORE-2774 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8723) Move elytron management security tests from full to core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-8723?page=com.atlassian.jira.plugin.... ] Ken Wills reassigned WFLY-8723: ------------------------------- Assignee: Ken Wills > Move elytron management security tests from full to core > -------------------------------------------------------- > > Key: WFLY-8723 > URL: https://issues.jboss.org/browse/WFLY-8723 > Project: WildFly > Issue Type: Task > Reporter: Ken Wills > Assignee: Ken Wills > > This is the wildfly portion of https://issues.jboss.org/browse/WFCORE-2746 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7649) Ensure initial context lookup using the "java:" prefix works with the new naming client

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7649?page=com.atlassian.jira.plugin.... ] Farah Juma resolved WFLY-7649. ------------------------------ Resolution: Done > Ensure initial context lookup using the "java:" prefix works with the new naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-7649 > URL: https://issues.jboss.org/browse/WFLY-7649 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 11.0.0.Beta1 > > > Currently, using the new naming client to perform initial context lookup using the "java:" prefix will result in the following exception: > {code} > WFNAM00026: No provider for found for URI: java > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:334) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:123) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2774) Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2774?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-2774: ------------------------------ Component/s: Domain Management Security Test Suite > Move org.jboss.as.test.manualmode.mgmt.elytron.HttpMgmtInterfaceElytronAuthenticationTestCase to wildfly-core > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2774 > URL: https://issues.jboss.org/browse/WFCORE-2774 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7649) Ensure initial context lookup using the "java:" prefix works with the new naming client

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7649?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-7649: ---------------------------------- This one should now be fixed by WFLY-8698 (the 1.0.0.Beta15 version of wildfly-naming-client contains a follow-up fix for WFNC-22 which should now allow JNDI lookups for names prefixed with "java:" to work properly). > Ensure initial context lookup using the "java:" prefix works with the new naming client > --------------------------------------------------------------------------------------- > > Key: WFLY-7649 > URL: https://issues.jboss.org/browse/WFLY-7649 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 11.0.0.Beta1 > > > Currently, using the new naming client to perform initial context lookup using the "java:" prefix will result in the following exception: > {code} > WFNAM00026: No provider for found for URI: java > at org.wildfly.naming.client.WildFlyRootContext.getProviderContext(WildFlyRootContext.java:334) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:123) > at org.wildfly.naming.client.WildFlyRootContext.lookup(WildFlyRootContext.java:113) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8700) Upgrade EJB client to 4.0.0.Beta27

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8700?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-8700: ------------------------------ Summary: Upgrade EJB client to 4.0.0.Beta27 (was: Upgrade EJB client to 4.0.0.Beta26) > Upgrade EJB client to 4.0.0.Beta27 > ---------------------------------- > > Key: WFLY-8700 > URL: https://issues.jboss.org/browse/WFLY-8700 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8726) Resources that expose capabilities cannot use a capability reference for legacy security-domain attributes

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-8726: -------------------------------------- Summary: Resources that expose capabilities cannot use a capability reference for legacy security-domain attributes Key: WFLY-8726 URL: https://issues.jboss.org/browse/WFLY-8726 Project: WildFly Issue Type: Bug Components: Security Reporter: Brian Stansberry Assignee: Brian Stansberry A number of resources expose 'security-domain' or similarly named attributes, the value of which is a legacy picketbox-based security domain. Referential integrity and value completion cannot be used for the attributes because the subsystem=security/security-domain resources do not expose a capability. This also relates to WFLY-3858 which was fixed via addition of a private capability to subsystem=security/security-domain for use by the infinispan subsystem. Better would be a normal public capability. Doing this will also mean tightening up the API exposed by the legacy security domain to remove methods that should not be available to callers outside the security subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 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 May 2017