My plan is to support configuration inheritance for form beans, forwards, exception handlers, and actions. Should I finish them all up, present them all, then check them in, or should I check in code as they become ready?
At the moment, form beans are done. Exceptions, forwards, and actions have supporting code done in the config objects; the wiring code is up next. So far, all the wiring is in the ActionServlet class because this is where the module startup code is. Joe had mentioned wanting to move module init code to the ModuleConfigFactory. Right now, ModuleConfigFactory is an abstract class with support for overriding the module config factory class and an abstract method declaration for "createModuleConfig(String prefix)". ( http://svn.apache.org/viewcvs.cgi/struts/core/trunk/src/share/org/apache/struts/config/ModuleConfigFactory.java?rev=57589&view=markup ) Init code would have to be moved here instead of the "concrete" DefaultModuleConfigFactory or it will cause compatibility issues. This can be done at a later date, of course, but in the meantime, about half of the ActionServlet code would be dedicated to initializing modules. Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
