[
https://issues.apache.org/jira/browse/WW-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694773#comment-17694773
]
Kusal Kithul-Godage commented on WW-5286:
-----------------------------------------
Interesting. In Confluence we are using this functionality to
register/deregister Actions and related entities during runtime. This is as we
have a modular plugin system where plugins can be installed/uninstalled at any
time. We also use it to update configuration options such as
struts.multipart.maxSize from within an Action.
> Allow XWork configuration reloading at any time
> -----------------------------------------------
>
> Key: WW-5286
> URL: https://issues.apache.org/jira/browse/WW-5286
> Project: Struts 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 6.1.1
> Reporter: Kusal Kithul-Godage
> Priority: Minor
> Fix For: 6.2.0
>
>
> Currently, if a
> {{com.opensymphony.xwork2.config.ConfigurationManager#reload}}
> or
> {{com.opensymphony.xwork2.config.ConfigurationManager#reloadProviders}}
> are triggered, any Struts requests that are in the process of being served,
> or commence serving during the reload, will malfunction.
> To make reloading the container configuration safe at any time, the reload
> should wait until any commenced requests are finished serving, and should not
> commence serving any new requests until the container reload is complete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
