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=21821>. 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=21821 taglibs requesting certain RequestUtil methods fail if page access not through ActionServlet ------- Additional Comments From [EMAIL PROTECTED] 2003-07-23 15:21 ------- The patch modifies RequestUtils.retrieveMessageResources to look for the message resource in the application context without a module prefix appending it, if there is no module config in the request scope. Unless, I'm missing something, this will only look to get the default module/application's message resources under that particular bundle name/key. This also doesn't address the issue of other methods like RequestUtils.pageUrl(...) that are being called from tags like html.LinkTag (through RU.computeUrl), which also rely on the current module's config being in the request scope. If the case is that we want to require users to use a real Model2 approach (not just "encourage"... semantics ;) then I would propose just changing the example applications to not access jsp pages directly in the request. This may surprise some users updating from versions of struts where this was not a "problem" though. I also can't think of any other situations where the current module config would not be in the request scope, since any other request I can think of should first pass through ActionServlet.process where RU.selectModule is called. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
