You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

The @Result annotation allows the definition of Action results in the Action class rather than an XML file.

The @Result annotation lives at the Action class level and not the method level. This matches what is found in an XML-based Action configuration. Do not be tempted to annotate your Action's methods; it will not work.

In order for @Result and @Results annotations to be configured correctly you must set the actionPackages filter init-param to a comma-separated list of packages containing the annotated Action classes. See Zero Configuration for further information; there are Action class naming conventions if you don't implement the Action interface and other tidbits there.

@Result Annotation Parameters

  • name - Result name; default Action.SUCCESS
  • value - Value of result (result destination)
  • type - Type of result; default NullResult. For example:
    • ServletRedirectResult
    • ServletActionRedirectResult - Equivalent to redirect-action type in XML config.
    • TilesResult
  • params

@Result – Defining a Single Result

Map the "success" result (explicitly named) to a Tile definition named "/home.page".

Defining a Single Result
@Result(name="success", value="/home.page", type=TilesResult.class)
public class HomeAction extends ActionSupport {
    // ...
}

@Results – Defining Multiple Results

Defines a set of results for an Action.

Defining Multiple Results
@Results({
    @Result(name="success", value="/home.page", type=TilesResult.class),
    @Result(name="homeError", value="/homeError.page", type=tilesResult.class)
})
public class HomeAction extends ActionSupport {
    // ....
}
Unknown macro: {dynamictasklist}
  • No labels