> Hi all,

> I've just tried out Guice for the first time today and it has
> impressed me... I've only touched the surface.

> Do all bindings have to be defined in the source code? I'd like to
> make that sort of thing runtime definable. Perhaps through an
> implementation of Module that searches the classpath for an
> appropriately named properties file (possibly "guice.properties") and
> sets up the bindings based on what it finds in there.

> It doesn't seem to hard to set it up... but before I go reinventing
> the wheel, does Guice have this functionality already?

> Thanks

> Bob

> On Nov 9, 2007 7:04 AM, Sam.halli...@gmail.com <Sam.Halli...@gmail.com> wrote:

> > Hi all,

> > I've just tried out Guice for the first time today and it has
> > impressed me... I've only touched the surface.

> > Do all bindings have to be defined in the source code? I'd like to
> > make that sort of thing runtime definable. Perhaps through an
> > implementation of Module that searches the classpath for an
> > appropriately named properties file (possibly "guice.properties") and
> > sets up the bindings based on what it finds in there.

> > It doesn't seem to hard to set it up... but before I go reinventing
> > the wheel, does Guice have this functionality already?

> > Thanks- Hide quoted text -

> - Show quoted text -

> public class PropertiesModule extends AbstractModule {

>     public void configure() {
>         Properties properties = new Properties();
>         try {
>             FileInputStream fis = new
> FileInputStream("Properties.xml");

>             properties.loadFromXML(fis);
>         } catch (IOException e) {
>             // throw exception
>         }

>         Names.bindProperties(binder(), properties);
>     }

> }

> public class MadLibs {
>     private final String name;
>     private final String verb;
>     private final String noun;

>     @Inject
>     public MadLibs(@Named("nameOfPerson")String name,
>             @Named("pastTenseVerb") String verb, @Named("noun")String
> noun) {
>         this.name = name;
>         this.verb = verb;
>         this.noun = noun;
>     }
>     public String getJoke() {
>         return "One day, " + name + " " + verb + " to New York to see
> the " + noun + ".";
>     }

> }

>     public static void main(String[] args) {
>         Module propertiesMoudule = new PropertiesModule();
>         Injector inj = Guice.createInjector(propertiesMoudule);
>         MadLibs madLibs = inj.getInstance(MadLibs.class);
>         String joke = madLibs.getJoke();
>         System.out.println(joke);
>     }

> Hope that helps.

> On Nov 9, 12:26 pm, "Bob Lee" <crazy...@crazybob.org> wrote:

> > Check out the Names class. It can convert a Properties into a Module
> > automatically.

> > Bob

> > On Nov 9, 2007 7:04 AM, Sam.halli...@gmail.com <Sam.Halli...@gmail.com> wrote:

> > > Hi all,

> > > I've just tried out Guice for the first time today and it has
> > > impressed me... I've only touched the surface.

> > > Do all bindings have to be defined in the source code? I'd like to
> > > make that sort of thing runtime definable. Perhaps through an
> > > implementation of Module that searches the classpath for an
> > > appropriately named properties file (possibly "guice.properties") and
> > > sets up the bindings based on what it finds in there.

> > > It doesn't seem to hard to set it up... but before I go reinventing
> > > the wheel, does Guice have this functionality already?

> > > Thanks- Hide quoted text -

> > - Show quoted text -- Hide quoted text -

> - Show quoted text -

> Thanks Rob and Adam... that was pretty much what I was after. Any
> thoughts on expanding on this functionality? Personally I was a little
> surprised that Guice didn't look for a properties (or horrible XML)
> file by default... or that there wasn't a simple convenience class for
> simply instantiating an Injector with a package-name based property
> reader like

>   Guice.createInjector(new PropertyModule("my.package"));

> I will probably do something like this... please let me know if you
> are aware of any problems with this technique. (Of course, defaults
> can be specified through annotations as usual).

> Bob

> On Nov 9, 2007 11:42 AM, Sam.halli...@gmail.com <Sam.Halli...@gmail.com> wrote:

> > Thanks Rob and Adam... that was pretty much what I was after. Any
> > thoughts on expanding on this functionality? Personally I was a little
> > surprised that Guice didn't look for a properties (or horrible XML)
> > file by default... or that there wasn't a simple convenience class for
> > simply instantiating an Injector with a package-name based property
> > reader like

> >   Guice.createInjector(new PropertyModule("my.package"));

> > I will probably do something like this... please let me know if you
> > are aware of any problems with this technique. (Of course, defaults
> > can be specified through annotations as usual).- Hide quoted text -

> - Show quoted text -