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=17823>.
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=17823

Problem with resouce bundles when working with multiple modules

           Summary: Problem with resouce bundles when working with multiple
                    modules
           Product: Struts
           Version: 1.1 RC1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Custom Tags
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


<html:errors>, <html:messages> and <beans:message> only work ok the first time 
called in a JSP page when using modules and when not explicitly specifying a 
resouce bundle in the Tag attribute. When they are called twice in the same 
page, the tags don't find the default bundle for the module the second time.

Suppose we have a module "instruments":

<html>
...
<bean:message key="title.createFund" />  <!-- ok -->
...
<bean:message key="label.fundCode"/>     <!-- nok -->
...
</html>

If the previous code is like follows it works:

<html>
...
<bean:message key="title.createFund" bundle='<%=Globals.MESSAGE_KEY 
+ "/instruments" %>' />  <!-- ok -->
...
<bean:message key="label.fundCode" bundle='<%=Globals.MESSAGE_KEY 
+ "/instruments" />      <!-- ok -->
...
</html>

I guess the tag is initialized ok (bundle=null) so it will look in the request 
scope first for the default bundle(Globals.MESSAGE_KEY + "/instruments"). When 
the release method is called, the bundle is not set to null, but to 
Globals.MESSAGE_KEY. When processing the tag a second time, the bundle is not 
null and the code will look immediately in the application scope for a bundle 
name Globals.MESSAGE_KEY which is the default application bundle and not the 
default module bundle.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to