October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3900) Unable to inject EJB Context into CDI Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3900: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1149644, https://bugzilla.redhat.com/show_bug.cgi?id=1149646 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1149644) > Unable to inject EJB Context into CDI Interceptor > ------------------------------------------------- > > Key: WFLY-3900 > URL: https://issues.jboss.org/browse/WFLY-3900 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > Attachments: inject-ejb-context-into-cdi-interceptor.jar, server.log > > > CDI Interceptor cannot inject EJB session context. > If the Interceptor is changed to EJB interceptor by removing the @Interceptor on the interceptor and removing it from the beans.xml, and adding @Interceptors(...) to the EJB, then it is able to inject. > See attached reproducer with source and log file. > private @Resource SessionContext sessionContext; > Caused by: javax.naming.NameNotFoundException: env/test.ServiceLoggedInterceptor/sessionContext -- service jboss.naming.context.java.comp.inject-ejb-context-into-cdi-interceptor.inject-ejb-context-into-cdi-interceptor.HelloEJB.env."test.ServiceLoggedInterceptor".sessionContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) > ... 127 more -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-117) Support for SSL/TLS protocol and algorithm filtering

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-117?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated ELY-117: ---------------------------- Description: Support OpenSSL-style filter expressions. Consider the following prior work for reference: * The GrokTLS project: https://github.com/timw/groktls * Previous unmerged enhancement to XNIO: https://github.com/xnio/xnio/pull/56 * APR/Native connector docs - http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_AP... * OpenSSL docs: ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_SUITE_NAMES (note that the OpenSSL names are non-standard) was: Support OpenSSL-style filter expressions. Consider the following prior work for reference: * The GrokTLS project: https://github.com/timw/groktls * Previous unmerged enhancement to XNIO: https://github.com/xnio/xnio/pull/56 * APR/Native connector docs - http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_AP... > Support for SSL/TLS protocol and algorithm filtering > ---------------------------------------------------- > > Key: ELY-117 > URL: https://issues.jboss.org/browse/ELY-117 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > Support OpenSSL-style filter expressions. Consider the following prior work for reference: > * The GrokTLS project: https://github.com/timw/groktls > * Previous unmerged enhancement to XNIO: https://github.com/xnio/xnio/pull/56 > * APR/Native connector docs - http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_AP... > * OpenSSL docs: > ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS > ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_SUITE_NAMES (note that the OpenSSL names are non-standard) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-102) MD5 Compatibility tests failing on Windows

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-102?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-102. ----------------------------- Fix Version/s: 1.0.0.Beta1 Resolution: Done Seems fixed. > MD5 Compatibility tests failing on Windows > ------------------------------------------ > > Key: ELY-102 > URL: https://issues.jboss.org/browse/ELY-102 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: David Lloyd > Assignee: Peter Skopek > Fix For: 1.0.0.Beta1 > > > The following tests fail on Windows or any platform which does not have UTF-8 as its default encoding: > * CompatibilityClientTest.testUtf8Charset > * CompatibilityServerTest.testUtf8Charset > Can be reproduced on Linux on the command line by setting the LANG environment variable to something other than UTF_8, like ISO-8859-1. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-101) GSSAPI failures on Windows

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-101?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-101. ----------------------------- Resolution: Done Seems fixed. > GSSAPI failures on Windows > -------------------------- > > Key: ELY-101 > URL: https://issues.jboss.org/browse/ELY-101 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Environment: Windows > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The following GSSAPI tests fail on Windows for reasons unknown (probably not character encoding though): > * BasicAuthTest.testAuth > * BasicConfidenceTest.testAuthConf > * BasicIntegrityTest.testAuthInt > * NoServerAuthTest.testAuth > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-28) Define Permissions Checks for org.wildfly.security.auth.provider.SecuritySystem

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-28?page=com.atlassian.jira.plugin.sys... ] David Lloyd resolved ELY-28. ---------------------------- Fix Version/s: (was: 1.0.0.Beta1) Resolution: Out of Date SecuritySystem is gone. > Define Permissions Checks for org.wildfly.security.auth.provider.SecuritySystem > ------------------------------------------------------------------------------- > > Key: ELY-28 > URL: https://issues.jboss.org/browse/ELY-28 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Darran Lofthouse > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-45) Add some form of isTranslatable to the API for password types.

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-45?page=com.atlassian.jira.plugin.sys... ] David Lloyd resolved ELY-45. ---------------------------- Resolution: Done > Add some form of isTranslatable to the API for password types. > -------------------------------------------------------------- > > Key: ELY-45 > URL: https://issues.jboss.org/browse/ELY-45 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > We have a method to check if a KeySpec conversion is possible from a password type, we should also have a method to check if the password type is translatable - i.e. if a call to translate is likely to be successful. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-114) Eliminate verifier API

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-114?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-114. ----------------------------- Resolution: Done > Eliminate verifier API > ---------------------- > > Key: ELY-114 > URL: https://issues.jboss.org/browse/ELY-114 > Project: WildFly Elytron > Issue Type: Task > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > The verifier API is almost certainly not useful. Let's just get rid of it. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-96) Password File backed KeyStore

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-96?page=com.atlassian.jira.plugin.sys... ] David Lloyd resolved ELY-96. ---------------------------- Resolution: Done > Password File backed KeyStore > ----------------------------- > > Key: ELY-96 > URL: https://issues.jboss.org/browse/ELY-96 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: David Lloyd > > A key store which stores modular-crypt style passwords. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-103) SCRAM password and Digest-MD5 password types live in different homes

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-103?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-103. ----------------------------- Resolution: Done > SCRAM password and Digest-MD5 password types live in different homes > -------------------------------------------------------------------- > > Key: ELY-103 > URL: https://issues.jboss.org/browse/ELY-103 > Project: WildFly Elytron > Issue Type: Bug > Reporter: David Lloyd > Assignee: David Lloyd > > The SASL DIGEST-MD5 password type is located in the sasl.password package, but the SASL SCRAM password type is in the main password package. We need to pick one place or the other for SASL password types. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-105) Add ability for configuration clients to create SaslClients directly from config

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-105?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-105. ----------------------------- Resolution: Done > Add ability for configuration clients to create SaslClients directly from config > -------------------------------------------------------------------------------- > > Key: ELY-105 > URL: https://issues.jboss.org/browse/ELY-105 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 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 October 2014