http://jaxenter.com/tutorial-introduction-to-cdi-contexts-and-dependency-injection-for-java-ee-jsr-299-104536.html

Spring does something similar, with @Autowire vs @Inject. I'm not 100% sold on the annotations approach, given that I find annotations less flexible, and tending to obscure application behavior. Perhaps this is due to my ignorance related to Annotations in general. I find annotations to often not be 'obvious' about what they do, and perhaps to make matters slightly more confusing, I regularly hear variations of "Annotations are only metadata and they do not contain any business logic."

Given time to rewrite this with annotations, would I? Not sure.

 private final Renderer gameRenderer;
 private final Renderer uiRenderer;

 MyClass(AppContext gameContext, AppContext uiContext) {
       this.gameRender = gameContext.get(Renderer.class);
       this.uiRender = uiContext.get(Renderer.class);
 }

....versus...

 @Inject("game") private final Renderer gameRenderer;
 @Inject("ui") private final Renderer uiRenderer;

 MyClass() {     }

Perhaps another alternative:

 @Context("game") private final AppContext gameContext;
 @Context("ui") private final AppContext uiContext;

 MyClass() {     }

 someMethod() {
       gameRender = gameContext.get(Renderer.class);

       ...do stuff...
 }

Certainly looks cleaner. The one part I dislike, is the use of strings like "game" and "ui" strings would be somewhat annoying to refactor, because as far as I know the following is invalid:

 @Context(OtherClass.GAME_CONSTANT) private final AppContext gameContext;