On Sunday, April 6, 2014 11:52:41 PM UTC+2, Christian Gruber wrote: > > I would load it, parse the property and bind it in a separate module. > As long as the value is bound (ideally with a qualifier/binding > annotation) then other things (including your constructors) can depend > on it properly. Trying to manually inject it into these other classes > is more work than you need to do. > > Could you please be so kind to explain that in more detail.
> Are you trying to convert all properties from spring, or specific > properties? Because you can make a special module that parses spring > configurations and binds the properties, but that's more work than maybe > you need, if you're just grabbing a few specific properties. > > Also, do these need to live in spring configuration xml files? > > The format is irrrelevant. (It is, in fact, an internal format, inherited from a home brewn DI framework, roughly like Plexus.) The important part is that I'd like to reserve the ability to have a single file, where 1.) I can specify bindings. Not necessarily all, but at least a few additional ones. 2.) I can configure the Pojos thus created at the same place. Thanks, Jochen -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice. For more options, visit https://groups.google.com/d/optout.
