February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-1006) JAPIC module's initialize() is called multiple times

by Hisanobu Okuda (Jira)

Hisanobu Okuda created SECURITY-1006: ---------------------------------------- Summary: JAPIC module's initialize() is called multiple times Key: SECURITY-1006 URL: https://issues.redhat.com/browse/SECURITY-1006 Project: PicketBox Issue Type: Bug Components: PicketBox Affects Versions: PicketBox_5_0_3.Beta1 Reporter: Hisanobu Okuda Assignee: Stefan Guilhen JAPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13141) JAPIC module's initialize() is called multiple times

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13141?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFLY-13141: ----------------------------------------- This is in the legacy PicketBox integration which is now deprecated, would recommend migrating to the WildFly Elytron configuration which is still actively maintained and developed. > JAPIC module's initialize() is called multiple times > ---------------------------------------------------- > > Key: WFLY-13141 > URL: https://issues.redhat.com/browse/WFLY-13141 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Beta1 > Reporter: Hisanobu Okuda > Priority: Major > > JAPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13141) JAPIC module's initialize() is called multiple times

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13141?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-13141: ------------------------------------ Component/s: Security (was: Web (Undertow)) > JAPIC module's initialize() is called multiple times > ---------------------------------------------------- > > Key: WFLY-13141 > URL: https://issues.redhat.com/browse/WFLY-13141 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Beta1 > Reporter: Hisanobu Okuda > Assignee: Flavia Rainone > Priority: Major > > JAPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13141) JAPIC module's initialize() is called multiple times

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13141?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFLY-13141: --------------------------------------- Assignee: (was: Flavia Rainone) > JAPIC module's initialize() is called multiple times > ---------------------------------------------------- > > Key: WFLY-13141 > URL: https://issues.redhat.com/browse/WFLY-13141 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 20.0.0.Beta1 > Reporter: Hisanobu Okuda > Priority: Major > > JAPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-306) Health check response contains default readiness data

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFWIP-306?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFWIP-306: ----------------------------------- This change is mentioned in the document: https://github.com/wildfly/wildfly-proposals/blob/dc28a32e484667452e5766f... It was added to fix WFLY-12952 that was done in 19.0.0.Beta2. It is *not* related to the MP Health 2.2 upgrade. As documented in the WildFly documentation, you can set mp.health.disable-default-procedures to true to keep the previous behaviour > Health check response contains default readiness data > ----------------------------------------------------- > > Key: WFWIP-306 > URL: https://issues.redhat.com/browse/WFWIP-306 > Project: WildFly WIP > Issue Type: Bug > Components: MP Health > Reporter: Fabio Burzigotti > Assignee: Jeff Mesnil > Priority: Critical > > Starting from Wildfly 19 Beta 2 and with current feature branch for MP Health upgrade to 2.2 [1], some tests started to fail, reporting unexpected content in JSON response. > When no _readiness_ health check procedures are defined for a given deployment - the returned JSON payload contains a "default" health check readiness object, conventionally named as "ready-deployment." + <archive-name> > The same _does not_ happen when there's just one registered readiness procedure - i.e. when no annotated _liveness_ procedures exist. > This change is not documented in the Analysis document: https://github.com/wildfly/wildfly-proposals/pull/284 > The following example uses an Arquillian deployment with a single HealthCheck implementation with _liveness_ health check procedure. > 1. feature branch [1] > {code} > //health > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > }, > { > "name": "ready-deployment.HealthTest.war", > "status": "UP" > } > ] > } > //live > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //ready > { > "status": "UP", > "checks": [ > { > "name": "ready-deployment.HealthTest.war", > "status": "UP" > } > ] > } > {code} > 2. here are the results for the same calls against Wildfly 19 Beta 1: > {code} > //health > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //live > { > "status": "UP", > "checks": [ > { > "name": "live", > "status": "UP", > "data": { > "key": "value" > } > } > ] > } > //ready > { > "status": "UP", > "checks": [] > } > {code} > [1] > https://github.com/jmesnil/wildfly -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13141) JAPIC module's initialize() is called multiple times

by Hisanobu Okuda (Jira)

Hisanobu Okuda created WFLY-13141: ------------------------------------- Summary: JAPIC module's initialize() is called multiple times Key: WFLY-13141 URL: https://issues.redhat.com/browse/WFLY-13141 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 20.0.0.Beta1 Reporter: Hisanobu Okuda Assignee: Flavia Rainone JAPIC module's initialize() is called multiple times. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13140) Upgrade smallrye-config from 1.4.1 to ...

by Lin Gao (Jira)

Lin Gao created WFLY-13140: ------------------------------ Summary: Upgrade smallrye-config from 1.4.1 to ... Key: WFLY-13140 URL: https://issues.redhat.com/browse/WFLY-13140 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Lin Gao Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12947) EL should coerce String to Integer in equals operation

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12947?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12947: ------------------------------------ Fix Version/s: 19.0.0.Beta3 20.0.0.Beta1 > EL should coerce String to Integer in equals operation > ------------------------------------------------------ > > Key: WFLY-12947 > URL: https://issues.redhat.com/browse/WFLY-12947 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 18.0.1.Final > Reporter: Ricardo Martin Camarero > Assignee: Ricardo Martin Camarero > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > EAP 7's EL equals operations work differently from EAP 6 one. > For example: put the following JSP in your web application (e.g. example.war) > {code:java|title=test.jsp} > <% request.setAttribute("testAttr", "01"); %> > ${testAttr == 1} > ${param['foo'] == 1} > ${1 == param['foo']} > ${1 == (0+param['foo'])} > {code} > Then, access the above JSP with curl command: > {code} > $ curl http://localhost:8080/example/test.jsp?foo=01 > {code} > - Expected result (EAP 6's behavior): > {code} > true > true > true > true > {code} > - Actual result (EAP 7's behavior): > {code} > false > false > false > true > {code} > In the section 1.9.2 of [EL 3.0 Specification|https://download.oracle.com/otndocs/jcp/el-3_0-fr-eval-spec...], the ==,!= operators have the following step: > {code} > ■If A==B, apply operator > ■ If A is null or B is null return false for == or eq, true for != or ne. > ■ If A or B is BigDecimal, coerce both A and B to BigDecimal and then: > ■ If operator is == or eq, return A.equals(B) > ■ If operator is != or ne, return !A.equals(B) > ■ If A or B is Float or Double coerce both A and B to Double, apply operator > ■ If A or B is BigInteger, coerce both A and B to BigInteger and then: > ■ If operator is == or eq, return A.equals(B) > ■ If operator is != or ne, return !A.equals(B) > ■ If A or B is Byte, Short, Character, Integer, or Long coerce both A and B to Long, apply operator > ■ If A or B is Boolean coerce both A and B to Boolean, apply operator > ■ If A or B is an enum, coerce both A and B to enum, apply operator > ■ If A or B is String coerce both A and B to String, compare lexically > ■ Otherwise if an error occurs while calling A.equals(B), error > ■ Otherwise, apply operator to result of A.equals(B) > {code} > Note that the step "If A or B is Byte, Short, Character, Integer, or Long coerce both A and B to Long, apply operator" should happen earlier than the step coercion to String. So, it appears that EAP 7's behavior violates the spec. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13139) Upgrade org.glassfish:jakarta-el from 3.0.3.jbossorg-1 to 3.0.3.jbossorg-2

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13139: --------------------------------------- Summary: Upgrade org.glassfish:jakarta-el from 3.0.3.jbossorg-1 to 3.0.3.jbossorg-2 Key: WFLY-13139 URL: https://issues.redhat.com/browse/WFLY-13139 Project: WildFly Issue Type: Component Upgrade Components: EE Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 19.0.0.Beta3, 20.0.0.Beta1 https://github.com/jbossas/el-ri/compare/3.0.3.jbossorg-1...3.0.3.jbossorg-2 Fixes WFLY-12947 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13138) BOM Builder feature to include transitives of a dependency

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13138: -------------------------------------- Summary: BOM Builder feature to include transitives of a dependency Key: WFLY-13138 URL: https://issues.redhat.com/browse/WFLY-13138 Project: WildFly Issue Type: Enhancement Components: BOM Reporter: Eduardo Martins Assignee: Eduardo Martins Add configuration to include transitives of a managed dependency, no matter the transitive scope. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 February 2020