Good point! I ran originally ran into the resource bundle problem a long time ago, and forgot that there are other application-wide settings that would be nice to inherit from module to module.
1) Declarative Exception Handling (<global-exceptions>) - in my application, each module treats exceptions the same way, so we end up copying the <global-exceptions> portion of the struts-config file from module to module. 2) Global Forwards - same deal with global forwards. We have a "debug" forward that we use when debugging Action classes that gets copied to every module(System.out.println isn't practical on some application servers, and we haven't implemented log4j yet, so "debug" isn't a great example, but I'm sure someone can think of a better one) Matt ----- Original Message ----- From: "adam kramer" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, August 06, 2003 11:52 AM Subject: Re: Resource Bundle Prototyping > > On Wed, 6 Aug 2003, Sgarlata Matt wrote: > > Has there been any discussion of allowing resource bundles to inherit > > properties from other resource bundles? For the project I am working > > on, it would be nice if we had one resource bundle with > > application-level properties and also module-specific resource bundles > > which had all the properties of the application-level resource bundle > > plus additional ones specific to that module. I know you can specify > > multiple resource bundles per module in Struts, but the problem is that > > certain components (e.g. - the validator) always look for the default > > resource bundle. > > In some of my projects I have run into the same problem as well, and I'm > sure others have. It would be nice to have either a core module that > provided resources to all modules or atleast a way of specifying a way for > a the default resource bundle in modules to inherit values from a core > resource bundle as to avoid having to repeat values throughout an > application and introduce chances for inconsistency and error. This might > be done by specifying an application-wide resource bundle in struts > configuration and then have those values within all other module resource > bundles (inclding the default module). You could obviously overwrite the > values in your module's def. bundle. This would seem an > appropriate feature, unless there were other core resources that needed to > be shared throughout modules. Then it would seem a module-type enhance > would be appropriate. ahh, oh so vague. :) > > -adam k. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
