Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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

Code Block
com.opensymphony.xwork.config.ConfigurationManager.destroyConfiguration() 
Info
titleUseful Information

This should destroy the current configuration and perform a config reload on next request. You can use a action for do it.

...

Code Block
titlewebworkstruts.properties
### Configuration reloading
### This will cause the configuration to reload xworkstruts.xml when it is changed
webworkstruts.configuration.xml.reload=false
true

Reloading the Configuration

Create a utility Action that calls reload.

Code Block
titleMyUtilityAction.java

// ...
String execute() {
  Dispatcher.getIntance().getConfigurationManager().reload();
  return SUCCESS;
}

Invoking reload will force Struts to reload the configuration.