DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30095>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30095 Clarify rules for direct access of JSPs when using Modules [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|html:form html response |Clarify rules for direct |error in multi-module |access of JSPs when using | |Modules ------- Additional Comments From [EMAIL PROTECTED] 2004-07-14 13:47 ------- I'm not sure whether this qualifies as a true bug or not, but it is an issue. In general, it is recommended that all access to your application be routed through Struts actions and that you deflect direct access to your JSPs. The main reason this is recommended is because it gives you freedom later to interpose processing before the view without rearranging your application or possibly invalidating URLs which may be bookmarked. For modules, this is more important, as it is the Struts RequestProcessor which determines the "active" module based on the request. When you access a JSP directly, this never happens, and so none of the JSP tags can take advantage of the RequestProcessor's determination of the ModuleConfig -- so this bug would apply to <html:link> tags which use the "action" attribute, and anything else which does module-aware URL rewriting. It might be possible to interpret a null ModuleConfig as a hint that some code should call "ModuleUtils.selectModule()" (This is done in TilesUtilStrutsModulesImpl.getModuleConfig) but there would probably be some unexpected side effects if current methods were changed to do that rather than returning null. Probably we ought to coin a new method which clearly has the intention of "get me the ModuleConfig, and use selectModule() if you have to." I am thinking that it never makes sense to have a null ModuleConfig in a Struts context, because even if you don't think you are using Modules, Struts uses a "default" ModuleConfig. So it may make sense to make this a more universal change, but I'd want a few other opinions before doing anything. In the meantime, the work-around is to design your application so that all requests come through Struts, even if many of your ActionMappings are just direct forwards to JSPs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
