May 2025 - wildfly-dev - Jboss List Archives

by Brian Stansberry

Currently we have a number of different repos publishing artifacts using the 'org.wildfly' groupId with no further namespacing. Going forward I don't think we should allow any other new repos to do that. It leads to administrative hassles, e.g. with setting things up in Nexus. Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

4 months, 1 week

7
16
0 / 0

Request for a feature team -- Promote Jakarta MVC support to community stability

by Brian Stansberry

We've supported Jakarta MVC at preview stability since WildFly 32. We've only had one bug report, and the management interface is as minimal as a subsystem could be, so I'd like to promote it to community stability for WildFly 37. If anyone would like to help out I'd be most appreciative. The feature issue: https://github.com/wildfly/wildfly-proposals/issues/607 The analysis: https://github.com/wildfly/wildfly-proposals/pull/717 The main work here will be moving the https://github.com/wildfly-extras/mvc-krazo-feature-pack code into the main WildFly repo or the wildfly-tck-runners repo. The production code work should be a simple new 'community' management API and schema version. The needed tests already exist. -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

1 year

3
9
2 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

1 year

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

1 year, 1 month

1
0
0 / 0

Request for a feature team -- Platform MBean evolution

by Jean Francois Denise

Hi, the WildFly management resources that expose JVM MXBeans in */core-service=platform-mbean* need a refresh and some evolutions. For full details on what is proposed, you can look at the WildFly proposal: https://github.com/wildfly/wildfly-proposals/pull/729 We have chosen to align to the JDK 11 API (with some exceptions to expose JDK 14 defined attributes that replace attributes introduced in JDK11 but already deprecated). This JDK 11 constraint is to align with WildFly core minimal supported version although the platform-mbean resource is used in WildFly that has a minimal version of JDK 17. We will continue this evolution to follow the minimal versions in order to avoid technical debt. Exposing new standard features We plan to expose new attributes and operations defined in the standard Platform MXBean API . Exposing the read-only attributes of the *PlatformLoggingMXBean* This MXBean is older than JDK 11 but has not been exposed due to potential conflict with the Logging subsystem. Although the management of loggers is done thanks to the logging subsystem, exposing the available loggers in the WildFly management model is a way to discover what are the logger names that one can enable using the logging subsystem. Exposing the attributes and operations defined in the *com.sun.management* package Attributes and operations defined by such MXBeans are aggregated to the existing WildFly resources. No new management resources are added. Although supported by all OpenJDK based JDK, this API is not standard. In order to cope with this, we are using the JMX reflective access to the attributes and operations allowing us to expose a static management model with an implementation that adapts to the JVM capabilities. The work on this feature is tracked by the PR: https://github.com/wildfly/wildfly-core/pull/6411 Brian (that implemented initially this integration) already volunteered to be an sme. Thank-you. JF

1 year, 1 month

3
3
0 / 0

Do we have any examples of WildFly formatting logger configuration that show the entire Exception call stack?

by Scott Marlow

I do not recall any way to configure WildFly to show the entire exception call stack in the console logger output. Does anyone have an example of doing that? Thanks, Scott

1 year, 1 month

2
3
0 / 0

Possible component upgrades report - wildfly-elytron:2.x

by thofman＠redhat.com

1 year, 1 month

1
0
0 / 0

Possible component upgrades report - elytron-web:4.x

by thofman＠redhat.com

1 year, 1 month

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

1 year, 1 month

1
0
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

1 year, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev May 2025