naming choices

One of the knocks against Struts is that configuration can be non-intuitive
due to some poor naming choices.  For the most part I think Maverick does a
much better job ... especially in the names used in maverick.xml files.

However, I think some of the choices for class names could be improved.  It
seems common when working on web applications to think about the lifetime of
data in terms of request, session and application scope.  Following that
thinking I'd make the following name changes.

ThrowAway2 --> RequestController
ThrowAwayBean2 --> RequestPropertyController
ControllerSingleton --> ApplicationController
FormBeanUser --> ApplicationFormBeanController
ThrowAwayFormBeanUser --> RequestFormBeanController

I don't see any supplied Controller subclasses that would correspond to
session scope ... where a new instance is created for each session.  I
suppose that isn't needed since you are free to place whatever data you'd
like in an HttpSession object.

Does anyone agree that these naming changes would make the purpose of the
classes more intuitive?


***********************************************************************************
WARNING:  All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
************************************************************************************