If your application routes to Java actions, then you must use this request handler as the base class as is or as the base class for your custom HttpRequestHandler.
The default is to use the application router to find the appropriate action.
This method can be overridden if you want to provide some custom routing strategies, for example, using different routers based on various request parameters.
Value parameters
request
The request
Attributes
Returns
A handler to handle the request, if one can be found
In addition to retrieving a handler for the request, the request itself may be modified - typically it will be tagged with routing information. It is also acceptable to simply return the request as is. Play will switch to using the returned request from this point in in its request handling.
The reason why the API allows returning a modified request, rather than just wrapping the Handler in a new Handler that modifies the request, is so that Play can pass this request to other handlers, such as error handlers, or filters, and they will get the tagged/modified request.
Value parameters
request
The request to handle
Attributes
Returns
The possibly modified/tagged request, and a handler to handle it