On Thu, Jun 11, 2009 at 10:33 PM, [email protected] <[email protected]>wrote:
> So I suppose I'd best fix the pollution issue, which will fix your > problem. Sorry for the pain; hopefully you're sympathetic to the > complexities involved here! > I knew it had something to do with getting caught up in the parent injector (because I saw two different bindings being created), but had no idea what the actual issue is. I'm still confused why the testcase with the same scenario didn't fail... but will wait to see how this issue resolves and will retry. I even tried using a PrivateModule for the child injector, but that failed with other errors (it still put some JIT bindings in the parent injector, and failed when the child injector tried to recreate those bindings). Thanks for taking a renewed look at this! If I can steal your attention for one more minute... take a look at http://code.google.com/p/google-guice/issues/detail?id=387 ? It's a patch to add binding listeners, which resolves a bunch of different issues relating to JIT eager singletons (in parent or child injectors), cleans up the hacky solution for issue 373, and is useful in general! Sam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
