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=16980>. 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=16980 ActionServlet.initModulePlugins loads plugins only until the first exception Summary: ActionServlet.initModulePlugins loads plugins only until the first exception Product: Struts Version: 1.1 Beta 3 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: Controller AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The first plugin which fails to initialize causes all the other plugins following it to not be loaded (see the plugin loading loop in ActionServlet.initModulePlugin()) To repeat simply misspell the className for a plugin before other plugins and you will see that your misspelled plugin is the last one loaded. Therefore the plugins are in a partially intialized state. It would be clearer if: I. all plugins were intialized and errors logged out along the way II. all plugins initialized and one aggregate exception was thrown III. all plugins de-initialized and web-app fails to "startup" if a plugin fails to load. I vote for choice I. But I don't really understand the struts/tomcat/servlet lifecycle very well. I saw this fail when I modified the struts sample application by deleting classes necessary for the MemoryBasedDatabasePlugin. It therefore failed to load, and the ValidatorPlugin failed to load. This caused a NullPointerException in a JSP trying to invoke the JavaScriptValidator.startTag() because its necessary resources were not loaded. (perhaps it should check?) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
