January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-895) AuthenticationConfiguration equals() and hashCode()

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-895?page=com.atlassian.jira.plugin.sy... ] David Lloyd reassigned ELY-895: ------------------------------- Assignee: David Lloyd > AuthenticationConfiguration equals() and hashCode() > --------------------------------------------------- > > Key: ELY-895 > URL: https://issues.jboss.org/browse/ELY-895 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > > We need AuthenticationConfiguration to have an equals() and hashCode() contract. Prerequisites to this are: > * Configurations must be commutative i.e. A+B == B+A > * Configurations must strictly eliminate similar items (we have a good start on this) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-749) String.toUpperCase() is used without Locale in AttributeMapping class (Elytron)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-749?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-749: --------------------------------- Fix Version/s: 1.1.0.Beta17 > String.toUpperCase() is used without Locale in AttributeMapping class (Elytron) > ------------------------------------------------------------------------------- > > Key: ELY-749 > URL: https://issues.jboss.org/browse/ELY-749 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Critical > Fix For: 1.1.0.Beta17 > > > The String.toUpperCase() call is used in constructor of {{AttributeMapping}} class without providing {{Locale.ENGLISH}} or {{Locale.US}} as parameter. > This can lead to problems on systems with non-English default locale (e.g. {{-Duser.language=tr}}). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-7396. ------------------------------------ Resolution: Done > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reopened WFLY-7396: ------------------------------------ > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7396: ----------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7396) No log messages comming from Elytron - exception handling

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7396?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7396: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > No log messages comming from Elytron - exception handling > --------------------------------------------------------- > > Key: WFLY-7396 > URL: https://issues.jboss.org/browse/WFLY-7396 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Log error messages from exceptions into log, where it can be useful. See https://issues.jboss.org/browse/JBEAP-6041 for more details. > It happened to me twice elytron doesn't log exceptions into log, which would be useful for me, but instead just ignore it. I get to them, once I was debugging code. > * https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147... > * https://github.com/wildfly-security/wildfly-elytron/blob/7666231fa76b95c3... > ** exceptin which was ignored here "java.security.PrivilegedActionException: GSSException: Unsupported mechanism requested: 1.2.840.48018.1.2.2" > Please review also other exception handling places, if exceptions are handled correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-4) Choose a license for the project

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-4?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro commented on AG-4: -------------------------------- After discussion with all the project stakeholders it was decided that the license that better enables the growth of the project is the Apache License 2.0 > Choose a license for the project > -------------------------------- > > Key: AG-4 > URL: https://issues.jboss.org/browse/AG-4 > Project: Agroal > Issue Type: Task > Components: infrastructure > Affects Versions: 0.0.0 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > > The project must have a License that governs the use and redistribution of the software -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-4) Choose a license for the project

by Luis Barreiro (JIRA)

Luis Barreiro created AG-4: ------------------------------ Summary: Choose a license for the project Key: AG-4 URL: https://issues.jboss.org/browse/AG-4 Project: Agroal Issue Type: Task Components: infrastructure Affects Versions: 0.0.0 Reporter: Luis Barreiro Assignee: Luis Barreiro The project must have a License that governs the use and redistribution of the software -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AG-3) Create a git repo for the connection pool source code

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-3?page=com.atlassian.jira.plugin.syste... ] Luis Barreiro resolved AG-3. ---------------------------- Fix Version/s: 0.0.1 Resolution: Done Available at https://github.com/agroal/agroal > Create a git repo for the connection pool source code > ----------------------------------------------------- > > Key: AG-3 > URL: https://issues.jboss.org/browse/AG-3 > Project: Agroal > Issue Type: Task > Components: infrastructure > Affects Versions: 0.0.0 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.0.1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-127) JDK 9 EA build 151 - Loggers not created

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-127?page=com.atlassian.jira.plu... ] James Perkins closed JBLOGGING-127. ----------------------------------- Resolution: Out of Date Excellent, thanks for testing it out. > JDK 9 EA build 151 - Loggers not created > ---------------------------------------- > > Key: JBLOGGING-127 > URL: https://issues.jboss.org/browse/JBLOGGING-127 > Project: JBoss Logging > Issue Type: Bug > Affects Versions: 3.2.1.Final > Reporter: Matej Novotny > Assignee: James Perkins > > I started looking into JDK 9 EA for [Weld|https://github.com/weld/core] and we use JBoss logging [there|https://github.com/weld/core/tree/master/impl/src/main/java/org/jbo...]. > Everything was working as expected with logging up until latest JDK EA build release (build 151). > Suddenly, after running build on JDK 9, no logger classes are generated and there is no error message either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017