From 78e8acd7a3f39a1f4028c3e7e48cf173d7a3b646 Mon Sep 17 00:00:00 2001 From: Mike Bierlee Date: Thu, 24 Dec 2015 23:10:56 +0100 Subject: [PATCH] Adjust tutorial a bit --- TUTORIAL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TUTORIAL.md b/TUTORIAL.md index fab853f..19559b3 100644 --- a/TUTORIAL.md +++ b/TUTORIAL.md @@ -186,12 +186,12 @@ application context, but don't neccesarily have to be. You can even autowire dep Application contexts are directly autowired after they have been registered. This means that all autowired dependencies which are not registered in the application context itself need to be registered before registering the application context. ###Controlling component registration -You can further influence how instances are registered and created with additional UDAs: +You can further influence how components are registered and created with additional UDAs: ```d class Context : ApplicationContext { @Component @Prototype // Will create a new instance every time the dependency is resolved. - @RegisterByType!SomeInterface // Registers the dependency by the specified super type so it can be resolved when a dependency of that super type is required. + @RegisterByType!SomeInterface // Registers the dependency by the specified super type instead of the return type public SomeClass someClass() { return new SomeClass(); }