Comment by [email protected]:
Actually Guice's programmatic approach (ie. Modules) and the SPI and custom
injection added in 3.0 makes it easy to support alternative metadata, such
as XML. As a proof of this, Guice replaced Plexus (an XML based container a
bit like Spring) in Maven3 while maintaining full compatibility with
plugins that had no Java5 annotations. It scrapes dependency details from
Plexus XML and uses Modules to programmatically feed them into Guice, the
SPI to perform analysis, and custom injection to wire everything up.
We're now actively using Guice to mimic a variety of different IoC
containers, allowing us to re-use legacy components across different
applications on a common framework and gradually migrate them to the JSR330
@Inject standard.
For more information:
http://code.google.com/p/google-guice/wiki/SpringComparison
--
You received this message because you are subscribed to the Google Groups
"google-guice-dev" 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-dev?hl=en.
