default message resources

[Erik Hatcher <er...@ehatchersolutions.com>]

I've seen how Tapestry's default message resource mechanism works, with 
each component getting their own set.  How does this default mechanism 
account for a globally accessible resource?  Or is it not possible?

I'm revamping my custom implementation to account for component-centric 
message resources, and that is working fine, and I've implemented in a 
global feature as well, such that components can override a default 
global message if they like.  I'm just curious how that compares to the 
default implementation.

Thanks,
	Erik


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