Page History

Most often, the Action Mappings will be automatically reloaded if the WAR is redeployed. If not, there are two things you can try: Setting the reload property to true and destroying the configuration.

Setting Reload to True

If you are finding that the xwork configuration is not reloaded when you redeploy your war. Is there a way to tell webwork to unload its configuration when the context is destroyed.

Try to call

com.opensymphony.xwork.config.ConfigurationManager.destroyConfiguration() 

another tip

This is another option that you can use, change for true.

### Configuration reloading
### This will cause the configuration to reload xwork.xml when it is changed
webworkaction.configuration.xml.reload=false
true

Destroying the Configuration

Create a utility Action that calls

com.opensymphony.xwork.config.ConfigurationManager.destroyConfiguration();

Invoking destryConfiguration should destroy the current configuration and force the configuration to be reloaded on next request (which you might want to make yourself!).