public WOResponse _handleRequest(WORequest request) {
// Retrieve the application object. We need to inform it of awake/sleep
// and use some of its helper methods.
WOApplication application = Application.app();
WOResponse response;
WOContext context;
application.awake();
try {
// Instantiate the action object for this request.
// The WOAction sets up the context and restores the session and so
// on.
WOAction action = new ContentAction(request);
// Retrieve the context object from the action.
context = action.context();
// Retrieve the content path. e.g. blog or blog/2009/10/10/foobar or
// whatever.
String contentPath = request.requestHandlerPath();
// TODO: We probably could use some exception handling here.
// 1. performActionNamed throws generating the WOActionResults
// 2. performActionNamed returns null
// 3. generateResponse throws
// 4. generateResponse returns null (although we do kind of handle
// this already).
// Ask the action object to handle the request. Unlike normal action
// objects the
// ContentAction object takes a path instead of the first part of a
// method name.
WOActionResults actionResults = action.performActionNamed(contentPath);
// Generate the response object.
if (actionResults != null) response = actionResults.generateResponse();
else response = null;
// FIXME: When we do add error handling, do we or don't we save the
// session in the
// event of an error?
if (context != null) {
// Check the session in to the session store. Particularly
// important if the
// session store is out of process.
application.saveSessionForContext(context);
}
} finally {
// End of request.
application.sleep();
}
// Ah, the joys of calling private APIs. For some reason both
// WOActionRequestHandler
// and WOComponentRequestHandler know about and call this method as
// virtually the
// last thing before returning the response. I am somewhat unclear as to
// why this
// method is private and why it isn't called by our caller instead of
// within the
// request handler.
// It is imperative that this method be called because it generates HTTP
// Set-Cookie
// headers from the NSArray<WOCookie>. Without this no cookies will ever
// function.
if (response != null) response._finalizeInContext(context);
return response;
}
