Class DispatchHandler
- All Implemented Interfaces:
 Handler
true, then the request
 is dispatched to the associated handler with no further processing.
 
 If no condition yields true then the handler will return a 404 not found response.
 Therefore, it's advisable to have a single "default" handler at the end of the list
 with no condition (unconditional) to handle otherwise un-dispatched requests.
- 
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic classCreates and initializes a dispatch handler in a heap environment. - 
Method Summary
 
- 
Method Details
- 
handle
Description copied from interface:HandlerReturns aPromiserepresenting the asynchronousResponseof the givenrequest. If any (asynchronous) processing goes wrong, the promise still contains aResponse(probably from the 4xx or 5xx status code family).A handler that doesn't hand-off the processing to another downstream handler is responsible for creating the response.
The returned
Promisecontains the response returned from the server as-is. This is responsibility of the handler to produce the appropriate error response (404, 500, ...) in case of processing error.Note: As of Promise 2.0 implementation, it is not permitted to throw any runtime exception here. Doing so produce unexpected behaviour (most likely a server-side hang of the processing thread).
 
 -