The action specified in the given ActionRequest is dispatched to a method in
the concrete controller whose name ends with "*Action". If no matching action
method is found, the action specified in $errorMethodName is invoked.
This controller also takes care of mapping arguments found in the ActionRequest
to the corresponding method arguments of the action method. It also invokes
validation for these arguments by invoking the Property Mapper.
By defining media types in $supportedMediaTypes, content negotiation based on
the browser's Accept header and additional routing configuration is used to
determine the output format the controller should return.
Depending on the action being called, a fitting view - determined by configuration
- will be selected. By specifying patterns, custom view classes or an alternative
controller / action to template path mapping can be defined.