Comment #1 on issue 545 by [email protected]: Improve the com.google.inject.name.Names properties resolution
http://code.google.com/p/google-guice/issues/detail?id=545
Forgot to mention that this Guice-approach is more powerful than the Spring one: I had a not so good experience with the Spring's [http://static.springsource.org/spring/docs/2.0.2/api/org/springframework/beans/factory/config/PropertyPlaceholderConfigurer.html PropertyPlaceholderConfigurer] because it forces users to centralize the Properties loading; I mean, to make things working, in the way that ${} expressions were correctly resolved, I had to declare just one PropertyPlaceholderConfigurer for the whole context, list all the *.properties files for the all modules.
I didn't like that approach at all, it doesn't allow users to split configurations in different modules even if some keys are shared by two or more modules. With this approach users won't have these problems at all, they can load Properties in different modules and obtain the same result.
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
