Re: [S2] Message Resources ExpressionConfigurationSupport

Yes, the problem with a wildcard search is that different containers or JVMs might sort the list differently. The current model already loads multiple property files from multiple location according to a predefined search pattern, and I expect it would handle the same way we handle them now, which

Re: [S2] Message Resources ExpressionConfigurationSupport

How will this handle key collisions in large projects? Or collisions with resources on the classpath that aren't easily modified? -bp Ted Husted wrote: I'm looking at which would let us load message resources by designating a package with a w

[S2] Message Resources ExpressionConfigurationSupport

I'm looking at which would let us load message resources by designating a package with a wildcard character, like this * webwork.custom.i18n.resources=ApplicationResources, actions/* in which case all the ".properties" files in the "actions" pac