Page History

...

Backward compatibility issues with previous versions

• Since 2.1.3: This settings need to be added to struts.xml to make the REST plugin work with the Codebehind plugin:

  Code Block
  xml xml
  <constant name="struts.codebehind.classSuffix" value="Controller"/> <constant name="struts.codebehind.action.checkImplementsAction" value="false"/> <constant name="struts.codebehind.action.checkAnnotation" value="false"/> <constant name="struts.codebehind.action.defaultMethodName" value="index"/> <constant name="struts.configuration.classpath.defaultParentPackage" value="rest-default" />

• Since 2.1.3: includeParams will default to none
• Since 2.1.3: cssClass and cssStyle attributes will be applied to the ul tags, instead of li in actionerror,actionmessage and fielderror tags
• Since 2.1.0: All default result names and interceptor names are now in camelCase (eg. was redirect-action, is now redirectAction)
• Since 2.1.0: The "ajax" theme is provided by the Dojo Plugin. Applications using the ajax theme must include the Dojo Plugin dependency and modify existing pages to import the plugin's own taglib/model
• Since 2.1.0 Tiles plugin: A DOCTYPE is now mandatory in the Tiles definitions XML
• Since 2.1.1: The immutable Configuration object is now created via a builder. The API is not compatible with prior versions. This primarily affects plugins that define Configuration.
• Since 2.1.1: The static method ActionContext.getContext() no longer lazily initializes an ActionContext. Unit tests that relied upon this behavior need to setup the ActionContext via the Container first.
• Since 2.1.1: OGNL method calls like "text(key)" now invoke "text(String)" instead of "getText(String)". This affects method calls only, not properties. Some OGNL expressions may need to be updated.
• Since 2.1.1: JUnit, TestNG, and DWR classes classes moved into their own plugins

...