I thought it was application module, therefore the current names are still consistent with that. Did I miss some threads :(
Wait, stop the printer... chuck > Going back to the discussion on calling modules "sub-applications", I think > it was decided to call everything a module to eliminate confusion. The > naming of Struts 1.1 classes and methods is not helping this situation. For > example, we have an ApplicationConfig class and > RequestUtils.selectApplication() methods. > > Maybe we should change these and others to ModuleConfig and selectModule()? > > Maybe I'm wrong but this seems to make it consistent. > > David > > _________________________________________________________________ > Choose an Internet access plan right for you -- try MSN! > http://resourcecenter.msn.com/access/plans/default.asp > > > -- > To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
