Comment #18 on issue 183 by mccu...@gmail.com: Scopes.SINGLETON uses a global lock
http://code.google.com/p/google-guice/issues/detail?id=183
OK, I've done some additional analysis of our use of the injector (it's encapsulated beneath a compatibility layer) and synchronizing at the binding level (as in the attached patch) is sufficient and correct for our particular use-case, but this is not strong enough proof for the generic case. As mentioned before, we've had problems with the class-level singleton lock in our particular framework (we have to support a large number of legacy components that we don't have control over) but then we can use our patched version as a workaround, without affecting users of stock Guice.
-- You received this message because you are subscribed to the Google Groups "google-guice-dev" group. To post to this group, send email to google-guice-dev@googlegroups.com. To unsubscribe from this group, send email to google-guice-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-guice-dev?hl=en.
