What happened is that many of the configuration options which used to be defined in web.xml are now defined in struts-config.xml instead. This is because they are now per-sub-app instead of being global settings for the web app.
In the particular case of message resources, there are two things to consider. First, each sub-app can specify its own message resources, which is why their configuration was moved to the struts-config.xml file. Second, it is quite common for a web app (or a sub-app) to have multiple resource bundles, so the DTD for the config file was extended to allow the loading of multiple resource bundles from a single struts-config.xml file. Note that it has always been possible for a Struts app to use multiple message bundles, and hence message resources. However, up until now, the app has always had to load additional bundles, beyond the default, by itself. Now Struts can load them for you. Also note that this new functionality is *not* the same thing as having multiple properties files presented to the application as a single message resource, which I think is what you are referring to. Although that has been suggested both here and in Commons, I don't believe it has been implemented in either place at this point. -- Martin Cooper ----- Original Message ----- From: "R�gis Brochu" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 28, 2002 7:33 AM Subject: message-ressources in struts-config.xml > Hi, > I saw last week the addition of many new properties in the > struts-config.xml (global-exceptions, controller, messages-resources, > etc). I'm really interested to know what the purpose of the > messages-resources property is. With this features are we going to be > able to split the resources files in more than one file like the Jakarta > Commons Resources package is supposed to do? > > I would really appreciate if you can give me some info on that > new Struts feature. > > Thanks > Redg > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
