[chain] What's the story with SelectModule?

[Joe Germuska <Jo...@Germuska.com>]

So I noticed tonight that the whole "servlet-complete" chain which is 
in the default chain-config isn't even the default; it's a mini-chain 
which offers to do some preprocessing and then 
calls"servlet-standard", which is the default.

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
Joe@Germuska.com
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction"  -The Ex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org