You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (Jira)" <ji...@apache.org> on 2023/06/28 07:00:00 UTC

[jira] [Updated] (WW-4483) Add Listener for Configuration events

     [ https://issues.apache.org/jira/browse/WW-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukasz Lenart updated WW-4483:
------------------------------
    Fix Version/s: 6.4.0
                       (was: 6.2.0)

> Add Listener for Configuration events
> -------------------------------------
>
>                 Key: WW-4483
>                 URL: https://issues.apache.org/jira/browse/WW-4483
>             Project: Struts 2
>          Issue Type: New Feature
>          Components: XML Configuration
>    Affects Versions: 2.3.20
>            Reporter: Jasper Rosenberg
>            Priority: Minor
>             Fix For: 6.4.0
>
>
> We have some rules that we enforce on our struts action and package configurations.  We currently enforce these by validating the configuration in non-production environments in a DispatcherListener.dispatcherInitialized() implementation.
> That works great at startup but, in development, I dynamically reload the configuration (say to fix an action definition), DispatcherListener.dispatcherInitialized() is not invoked, and so the configuration I reloaded is not revalidated.
> It would be great if struts2 supported a ConfigurationListener interface that could listen for at least init complete, and reload complete events.  I could see a lot of practical uses for that.  Thanks!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)