JSR-299 CDI / Weld vs. Google Guice

Posted by deamon on Stack Overflow See other posts from Stack Overflow or by deamon
Published on 2010-04-16T10:22:37Z Indexed on 2010/04/16 10:23 UTC
Read the original article Hit count: 1100

Filed under:
|
|
|
|

Weld, the JSR-299 Contexts and Dependency Injection reference implementation, considers itself as a kind of successor of Spring and Guice.

CDI was influenced by a number of existing Java frameworks, including Seam, Guice and Spring. However, CDI has its own, very distinct, character: more typesafe than Seam, more stateful and less XML-centric than Spring, more web and enterprise-application capable than Guice. But it couldn't have been any of these without inspiration from the frameworks mentioned and lots of collaboration and hard work by the JSR-299 Expert Group (EG).

http://docs.jboss.org/weld/reference/latest/en-US/html/1.html

What makes Weld more capable for enterprise application compared to Guice? Are there any advantages or disadvantages compared to Guice? What do you think about Guice AOP compared to Weld interceptors? What about performance?

© Stack Overflow or respective owner

Related posts about dependency-injection

Related posts about cdi