DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14054>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14054 Rename "Application" components to "Module" ------- Additional Comments From [EMAIL PROTECTED] 2002-11-04 17:41 ------- So how do we get this process started again ? I apologize if any comments I made about the the ActionMapping->ActionConfig were hasty, judgemental, or offended anyone. My concern right now if to get this process going again. Since the deprecated code will only exist through Struts 1.1 I would be a +1 on --whatever-- method we choose. Should we call for a consensis vote ? I do believe we should provide a deprecation path for users, Whatever method we use, providng a deprecation path will only cost us about 10 minutes more than a straight rename. I would like to make one more suggestion through, and that is to go ahead and use an interface at the back end of the process ModuleConfig - Interface ^ | StandardModuleConfigImpl - Existing ApplicationConfig code ^ | ApplicationConfig - Deprecated Method name. Delay adding a FactoryMethod for 1.1. Otherwise for 1.1->1.2 we might go through this renaming again, when/if other ModuleConfig schemes are implemented. By doing an interface now we reserve the name ModuleConfig for the concept it represents and not the implementation. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
