[
https://issues.apache.org/jira/browse/DELTASPIKE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994587#comment-15994587
]
ASF subversion and git services commented on DELTASPIKE-1245:
-------------------------------------------------------------
Commit d64cab49570a26094a8caaa7698d9a1c7fdce624 in deltaspike's branch
refs/heads/master from [~struberg]
[ https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;h=d64cab4 ]
DELTASPIKE-1245 improve MBean handling
> [Config] expose config via JMX bean
> -----------------------------------
>
> Key: DELTASPIKE-1245
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1245
> Project: DeltaSpike
> Issue Type: New Feature
> Affects Versions: 1.7.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.8.0
>
>
> It would be nice if the Configuration of an application could be exposed via
> JMX bean.
> Currently there is no easy way to have the Ops team look how an application
> is configured.
> This is not about checking a single configured value but the whole
> configuration system!
> I've built a JSF page for a customer which gets copied around from one
> project to the other.
> But it would be much better to expose those values via JMX by default. That
> way we would not need any user interface part, not much security (JMX is
> secured anyway), no JSF, etc.
> What information does get exposed?
> 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.
> With this information the Ops team can perform the right tweaks much more
> easily.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
