[
https://issues.apache.org/jira/browse/GERONIMO-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed GERONIMO-6567.
-----------------------------------
Resolution: Won't Fix
Closing old outdated issues.
Note that the Apache Geronimo Application Server itself was declared EOL in
2017 and we do not maintain the server parts anymore.
We still do actively maintain many of the Java EE / Jakarta EE which saw the
light during creation of the Apache Geronimo Aplication Server.
If you feel that this ticket still affects one of those components then please
feel free to reopen the ticket.
thanks, your Apache Geronimo team!
> Expose configuration system details via JMX
> -------------------------------------------
>
> Key: GERONIMO-6567
> URL: https://issues.apache.org/jira/browse/GERONIMO-6567
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Config
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
>
> This is basically the same functionality as we are currently implementing in
> DeltaSpike Config as well
> https://issues.apache.org/jira/browse/DELTASPIKE-1245
> Each application should be able to expose details about it's configuration
> via a MBean (JMX).
> The following info should be made available
> 1.) The list of all picked up ConfigSources + their ordinals. Of course
> already sorted
> 2.) All configured values.
> - their key
> - their 'native' value (without variables, etc)
> - the ConfigSource from which the value effectively got picked up
> Map of all the ConfigSources containing the key + the values which got
> resolved on each level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
