cascading messageresource lookups

[Wayne Christian <wa...@genesyslab.com>]

We've got a situation where a customer wants to have the option of
providing overrides to some of the contents of our message resource
file.  This could occur during rebranding, if a customer essentially
sells our software under their own brand name.  We're trying to see if
its possible for Struts to have a MessageResource lookup system where
when provided a key, it looks in fileA first and if that key is not
found, then it looks in fileB.  This is sort of how the Properties
class works, in that you can construct a default location that gets
searched if the loaded properties dont have the key.
Has anyone tried something like this?  Are there any thoughts about
what it might take to subclass MessageResources
(PropertyMessageResources?) or the factory in order to provide this
feature?  How would one hook this into struts so that struts would use
our overridden message class instead of its own?




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: cascading messageresource lookups

[James Mitchell <jm...@apache.org>]

Did you ever get a response on this?



--
James Mitchell
Software Engineer / Open Source Evangelist
EdgeTech, Inc.
678.910.8017
AIM: jmitchtx

----- Original Message ----- 
From: "Wayne Christian" <wa...@genesyslab.com>
To: <st...@jakarta.apache.org>
Sent: Thursday, December 09, 2004 10:04 AM
Subject: cascading messageresource lookups


> 
> We've got a situation where a customer wants to have the option of
> providing overrides to some of the contents of our message resource
> file.  This could occur during rebranding, if a customer essentially
> sells our software under their own brand name.  We're trying to see if
> its possible for Struts to have a MessageResource lookup system where
> when provided a key, it looks in fileA first and if that key is not
> found, then it looks in fileB.  This is sort of how the Properties
> class works, in that you can construct a default location that gets
> searched if the loaded properties dont have the key.
> Has anyone tried something like this?  Are there any thoughts about
> what it might take to subclass MessageResources
> (PropertyMessageResources?) or the factory in order to provide this
> feature?  How would one hook this into struts so that struts would use
> our overridden message class instead of its own?
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org