Could take another route and rather than worry about binding the individual settings, encapsulate the settings into a MailSettings class, create a Provider for MailSettings, then add the Provider<MailSettings> as a dependency to your classes requiring that information, or the MailSettings class itself as a dependency, depending on usage. Added bonus of adding as many attributes as you want down the road. If you can't modify those constructors/classes, create a builder that uses MailSettings to populate the string parameters.
-- You received this message because you are subscribed to the Google Groups "google-guice" 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?hl=en.
