Hi folks,
I've been busy documenting a set of modules over at Eclipse/Sisu that help
simplify working with Guice:
Guice.createInjector(
new WireModule( // auto-wires unresolved
dependencies
new SpaceModule( // scans and binds @Named
components
new URLClassSpace( classloader ) // abstracts class/resource
finding
) ) );
http://www.eclipse.org/sisu/docs/tutorials/javadoc.html
5 minute demo:
http://www.eclipse.org/sisu/docs/tutorials/index.html
These modules + Guice form the foundation of the Sisu container which is used
by applications such as Nexus and Maven 3.x.
The general idea is to use the Guice SPI to analyze the elements of modules
passed into the WireModule and automatically add bindings for any missing
dependencies. By default these automatic bindings are bound to a locator that
can query over multiple injectors, which lets us support various dynamic plugin
and configuration models. This kind of automatic approach is not for everyone,
but you could configure the WireModule to just do analysis or use your own
wiring strategy - and others might be interested in how it uses the Guice SPI
in general.
PS. we're near to making our first release from the Eclipse incubator (having
moved there from https://github.com/sonatype/sisu) ... until then the latest
milestone (M5) is considered stable wrt. API.
--
Cheers, Stuart
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/groups/opt_out.
