But surely you have name them in each struts-config.xml files differently? In which case there should be no need to specify the bundle in the bean:message taglib. That's the way I understood it - I don't actually use modules.

On 02/27/2004 05:53 PM David Adelson wrote:
Thanks. I am doing this.
This is why I am having trouble.
I have seperated my files and each is named
in struts-config.

If I want a property from the correct resource using
bean:message I just do,
<bean:message bundle="BundleNameInStrutsConfig" key="whatever">

BUT, actionerrors will not do it:
ActionErrors errors = new ActionErrors();
errors.add("name", new ActionError("keyinpropertiesfile"));

IE, there is no way to tell it which bundle (file) to use.

-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 11:42 AM
To: Struts Users Mailing List
Subject: Re: action errors and resource bundles


Er, hold on a moment. If you use modules, then you can specify a different properties file in each struts-config.


On 02/27/2004 05:21 PM David Adelson wrote:

thanks for the reply.
I was all excited about splitting up my properties files
for "common", "module1", and "module2".

But now it appears that all the errors we use all
have to be in one properties file.

bummer.



-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]
Sent: Friday, February 27, 2004 11:15 AM
To: Struts Users Mailing List
Subject: Re: action errors and resource bundles


On 02/27/2004 05:04 PM David Adelson wrote:



I have numerous property files for storing
my resources (applicationresources.properties).
Each one has a bundle name identified in struts-config.

Is there a way for ActionError or ActionMessage to get data from a particular bundle?


LOoking at the javadoc for ActionMessages, I would say no, it must be hard-coded to get it from the default bundle.

Adam





--
struts 1.1 + tomcat 5.0.16 + java 1.4.2
Linux 2.4.20 Debian


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



Reply via email to