doc: howto-create-concern minor rewording, fixing an inconsistency
Project: http://git-wip-us.apache.org/repos/asf/zest-qi4j/repo Commit: http://git-wip-us.apache.org/repos/asf/zest-qi4j/commit/42778a22 Tree: http://git-wip-us.apache.org/repos/asf/zest-qi4j/tree/42778a22 Diff: http://git-wip-us.apache.org/repos/asf/zest-qi4j/diff/42778a22 Branch: refs/heads/develop Commit: 42778a22036213c3360fee04c6573c38ece151c4 Parents: 3ed4896 Author: Paul Merlin <[email protected]> Authored: Sat Jan 24 13:41:10 2015 +0100 Committer: Paul Merlin <[email protected]> Committed: Sat Jan 24 13:41:10 2015 +0100 ---------------------------------------------------------------------- manual/src/docs/tutorials/howto-create-concern.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/zest-qi4j/blob/42778a22/manual/src/docs/tutorials/howto-create-concern.txt ---------------------------------------------------------------------- diff --git a/manual/src/docs/tutorials/howto-create-concern.txt b/manual/src/docs/tutorials/howto-create-concern.txt index a22aa07..9b319f5 100644 --- a/manual/src/docs/tutorials/howto-create-concern.txt +++ b/manual/src/docs/tutorials/howto-create-concern.txt @@ -19,8 +19,8 @@ source=tutorials/introduction/tenminutes/src/main/java/org/qi4j/demo/tenminute/I tag=allClass ----------- -The InventoryConcern is implemented as an abstract class, since we are not interested in the many other methods in the -Order interface. Extending the ConcernOf is a convenience mechanism, instead of an explicit @ConcernFor annotation on +Note that we could have implemented the InventoryConcern as an abstract class if we were not interested in __all__ the methods in the Order interface. +Extending the ConcernOf is a convenience mechanism, instead of an explicit @ConcernFor annotation on a private field, which can be used in rare occasions when you are not able to extend. This base class defines the next field, which is set up by the Qi4j runtime and points to the next fragment in the call stack. We can also see that the InventoryService is provided to the concern, which is done with dependency injection. Qi4j also supports dependency
