|Home > Guides > Core Developers Guide > ActionMapper > RestfulActionMapper|
A custom action mapper using the following format:
You can have as many parameters you'd like to use. Alternatively the URL can be shortened to the following:
This is the same as:
Suppose for example we would like to display some articles by id at using the following URL sheme:
Your action just needs a setArticleId() method, and requests such as /article/1, /article/2, etc will all map to that URL pattern.
Improved restful action mapper that adds several ReST-style improvements to action mapping, but supports fully-customized URL's via XML. The two primary REST enhancements are:
These two improvements allow a GET request for 'category/action/movie/Thrillers' to be mapped to the action name 'movie' with an id of 'Thrillers' with an extra parameter named 'category' with a value of 'action'. A single action mapping can then handle all CRUD operations using wildcards, e.g.
This mapper supports the following parameters:
The following URL's will invoke its methods:
To simulate the HTTP methods PUT and DELETE, since they aren't supported by HTML, the HTTP parameter "__http_method" will be used.
The syntax and design for this feature was inspired by the REST support in Ruby on Rails. See Simple RESTful support
To use the Restful2ActionMapper in an existing struts application we have to change the strus.mapper.class constant and let it point to the Restful2ActionMapper
The problem with the above approach is that we may break existing actions because the Restful2ActionMapper tries to guess the method name using conventions that aren't applicable to normal action classes.
To overcome the above problem, we have to use a different action mapper depending on the url we want to process. REST actions will be processed by the Restful2ActionMapper and non-REST actions by the DefaultActionMapper
To achieve that we have to rely on namespaces and the PrefixBasedActionMapper that can choose which action mapper to use for a particular url based on a prefix (the action namespace).
To put everything together, we create a package for our rest actions
All other actions remain in their existing packages and namespaces we use the PrefixBasedActionMapper telling it to use the Restful2ActionMapper for actions in the /rest namespace and the DefaultActionMapper for all other actions
For the Restful2ActionMapper to work we also have to set
Below you will find a simple unit test to test how to test actions when
Restful2ActionMapper is used.
Thanks to Antonios Gkogkakis for the examples!