From 91cf638e3a1f9e6063aeaebad4986a138adbd648 Mon Sep 17 00:00:00 2001 From: Michael Hunger Date: Sun, 17 Apr 2011 15:58:24 +0200 Subject: [PATCH] documentation update tutorial --- src/docbkx/tutorial/annotations.xml | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/src/docbkx/tutorial/annotations.xml b/src/docbkx/tutorial/annotations.xml index 46c5c43ad..7a77a617c 100644 --- a/src/docbkx/tutorial/annotations.xml +++ b/src/docbkx/tutorial/annotations.xml @@ -12,19 +12,15 @@ Property fields were taken care of automatically. - It was time to put our application to a test. First we needed to figure out how to persist our - entity to the database. It turns out that the aspect introduced new methods into the annotated - entities. For persisting the entity to the database, we used entity.persist(). - - - How could we now be assured that a field really was persisted to the graph store? + It was time to put our entities to a test. How could we now be assured that a attribute really was persisted to + the graph store? We wanted to load the entity and check the attribute. - Well, either we could have a GraphDatabaseContext injected and use its getById(entityId) - method, or use a more versatile Repository. We decided to keep things simple for now. To get an - entity's ID, we simply used the aspect-introduced method entity.getNodeId(). + Either we could have a GraphDatabaseContext injected and use its getById(entityId) + method to load the entity. Or use a more versatile Repository. We decided to keep things simple for now. Looking at the documentation revealed that there are a bunch of methods introduced to the - entities by the aspects. It's not entirely obvious, but we found two that would do the job: + entities by the aspects to support working with the entities. + That's not entirely obvious. We found two that would do the job: entity.persist() entity.getNodeId().