Issue Details (XML | Word | Printable)

Key: XW-235
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Patrick Lightbody
Reporter: Matt Raible
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
XWork

bundle specified with webwork.custom.i18n.resources not read everywhere

Created: 19/Sep/04 06:10 PM   Updated: 23/Aug/05 10:15 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Environment: Windows XP, JDK 1.4.2, Tomcat 5.0.28


 Description  « Hide
I have the following specified in my webwork.properties file:

webwork.custom.i18n.resources=ApplicationResources

I've found that using getTexts() inside my Action doesn't return this bundle. However, all calls to getText() do work with this bundle.

Also, I found that if I implement ModelDriven on my Action, the following shows up with no label:

    <ww:textfield label="getText('user.username')" name="'user.username'" value="user.username" required="true"/>

However, if I don't implement ModelDriven, then getText('user.username') works fine. If I create a .properties file for my Action with 'user.username' as a key in it - the label resolves fine with ModelDriven.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Jason Carreira added a comment - 14/Nov/04 12:01 PM
Where is the user.username text defined? Is it in your ApplicationResources global resourcebundle?

Matt Raible added a comment - 14/Nov/04 04:43 PM
Yes, all my messages are in one file - ApplicationResources.properties.

Mark Woon added a comment - 07/Mar/05 01:49 PM
Matt, is your ApplicationResources.properties in the root of your classpath? Or is it in your package hierarchy? If the latter, you'll need to specify the full path (e.g. org.matt.webapp.ApplicationResources).

Matt Raible added a comment - 07/Mar/05 01:56 PM
Yes, this file is in the root of my classpath - in WEB-INF/classes.

Patrick Lightbody added a comment - 23/Aug/05 10:15 PM
Matt -- I can't reproduce this problem in CVS anymore. I think it was either user error or got fixed due to other changes in LocalizedTextUtil.