Dhanji, How am I supposed to use GuiceFilter when I have multiple injectors and web servers running in the same JVM? Each unit test is supposed to run against its own injector and web server, unfortunately I don't understand how to set GuiceFilter.injectedPipeline so all unit tests end up hitting the same web server.
I noticed that GuiceServletContextListener creates the Injector *after* GuiceFilter is instantiated by the web container. How are we supposed to make this work? None of the Guice unit tests seem to demonstrate the usage of GuiceServletContextListener and GuiceFilter at the same time. Please help. Gili On Jun 16, 10:17 pm, cowwoc <[email protected]> wrote: > Hi, > > I just filedhttp://code.google.com/p/google-guice/issues/detail?id=636 > > I'm wondering if anyone has successfully run GuiceFilter in a highly > concurrent environment where you were creating and tearing down > servers concurrently. The usage of GuiceFilter.pipeline doesn't look > too thread-safe. > > Thanks, > Gili -- 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.
