So in looking at the SelectModule command, it's difficult to justify its existence. It looks up the ModuleConfig, which was already done by the ComposableRequestProcessor, and it puts MessageResources into the context, but they are apparently never missed by the default commands, since that command wasn't executing on most people's chains.
As of now, I'm not creating an ActionContext instance in the ComposableRequestProcessor, but rather leaving that up to a command in the chain -- so I'm not making any changes to the SelectModule command. But, since I don't see it's purpose, I think I'm going to take it out of the default chain in my working copy.
Joe
-- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
