Well that's a good point. I assumed I was doing something wrong on the Guice Module side because I couldn't find any examples doing what I'm trying to do there. And it seems like magic how Guice understands that it has to call the @Provides method to get back an object of type Bar. I guess I'm wondering if I need to tell it somehow ... am I missing something? Should the code above work?
One thing I wondered ... do I need to add this line to the configure() method: ... binder.bind(Bar.class); Again, how does it know that to construct Foo it will need a Bar, and to construct a Bar it needs to call FooModule.provideBar()? This is the source of my confusion and why I think I'm doing something wrong here. On Friday, July 26, 2013 2:27:05 PM UTC-5, Sam Berlin wrote: > > The stack trace doesn't appear to have anything to do with Guice. I'm not > really familiar with resteasy -- are you certain it's actually using Guice? > It looks to me like it's just doing its own thing and failing. > > -- 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/groups/opt_out.
