Dependency injection is a good technique to use throughout an application, imo, whether you are writing business logic to handle servlet requests, jms messages, or even just asynchronous messages between objects, so I don't see why Guice wouldn't make sense.
I can't comment on existing event-driven frameworks, and whether or not they integrate well with Guice. I can say that I've used Guice in a homegrown event handling framework built just on the Java Executors API, and it has worked quite well. I'm working on writing an event- based scope, where object lifecycles are limited to the life of an event, using thread-local to store objects that are to be injected into business logic. We'll see how that goes... On Feb 23, 2:12 pm, zixzigma <[email protected]> wrote: > I am sorry if this is not related to Guice. > within Guice API I noticed several classes related to Servlet, Persistence, > as a result I want to ask you about a feature not related to DI. > > what do you think about support for Asynchronous/Event Driven communication > between objects ? > do you use this technique in your development ? what framework do you use, > and does it make sense to add this to Guice ? -- 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.
