Skip to Content

Wiki source code of Your First Rest Project

Version 48.1 by Filippo Laurìa on 2013/09/06 11:02
Hide last authors
Filippo Laurìa 21.1 1
Filippo Laurìa 46.1 2
3 {{toc/}}
4
Pascal Robert 5.1 5 = Introduction =
6
7 In the first part of the Blog tutorial, you will learn:
8
9 * How to create a EOModel for the database (we will use H2)
10 * How to use migrations to create the database tables
11 * How to use ERRest to create blog posts with JSON format and how to display the blog posts in HTML for readers
12
Pascal Robert 30.1 13 = Create a new project =
14
Filippo Laurìa 47.1 15 You will need to create a new project for this tutorial. In Eclipse, open the **File** menu, select **New** and select **Wonder REST Application** (or **ERRest Application**, according to //your// WOLips version). Name your project as //BlogRest//.
Pascal Robert 30.1 16
Pascal Robert 5.1 17 = Create the database model =
18
Pascal Robert 30.1 19 == Database structure ==
20
Pascal Robert 5.1 21 We will build a small database model for the blog. The database will have two tables: BlogEntry and Author.
22
23 BlogEntry will have the following columns:
24
Filippo Laurìa 46.1 25 |=(((
26 Column name
27 )))|=(((
28 Type
29 )))|=(((
30 Constraints
31 )))
32 |(((
33 id
34 )))|(((
35 integer
36 )))|(((
37 primary key
38 )))
39 |(((
40 title
41 )))|(((
42 string(255)
43 )))|(((
44
45 )))
46 |(((
47 content
48 )))|(((
49 string(4000)
50 )))|(((
51
52 )))
53 |(((
54 creationDate
55 )))|(((
56 timestamp
57 )))|(((
58
59 )))
60 |(((
61 lastModified
62 )))|(((
63 timestamp
64 )))|(((
65
66 )))
67 |(((
68 author
69 )))|(((
70 integer
71 )))|(((
72 relation with Author
73 )))
Pascal Robert 5.1 74
75 Author will have the following columns:
76
Filippo Laurìa 46.1 77 |=(((
78 Column name
79 )))|=(((
80 Type
81 )))|=(((
82 Constraints
83 )))
84 |(((
85 id
86 )))|(((
87 integer
88 )))|(((
89 primary key
90 )))
91 |(((
92 firstName
93 )))|(((
94 string(50)
95 )))|(((
96
97 )))
98 |(((
99 lastName
100 )))|(((
101 string(50)
102 )))|(((
103
104 )))
105 |(((
106 email
107 )))|(((
108 string(100)
109 )))|(((
110 unique
111 )))
Pascal Robert 5.1 112
Pascal Robert 30.1 113 == Creating the EOModel ==
114
Pascal Robert 5.1 115 To create the database, we will first create a EOModel and use migrations to build the database on the file system (H2 will take care of creating the database file).
Pascal Robert 30.1 116
117 An EOModel consists of entities, attributes and relationships. When using it in a RDBMS context, an entity is a table (or a view), an attribute is a table column and a relationship is a join between two tables.
118
Filippo Laurìa 46.1 119 To create the EOModel, in the project right-click on the project name and select **New** -> **EOModel**.
Pascal Robert 30.1 120
121 Name it **BlogModel** and in the plugin list, select **H2**. Click **Finish**.
122
123 The model should show up in a window that looks like this:
124
Filippo Laurìa 46.1 125 [[image:attach:EOModeler.png]]
126
Pascal Robert 30.1 127 If it didn't show up, the window might have opened behind the main Eclipse window. If that's the case, open the **Window** menu and select the windows that have //Entity Modeler// in its name.
128
Filippo Laurìa 46.1 129 In the Entity Modeler window, click on **Default**, and for the **URL** field, type
Pascal Robert 30.1 130
Filippo Laurìa 46.1 131 {{code}}
132 jdbc:h2:~/BlogTutorial
133 {{/code}}
134
135 . When the database will be created, it will be stored in your home directory (/Users/youruser/ on OS X).
136
Filippo Laurìa 48.1 137 You can also specify an absolute path where to store in you h2 database files. For example on Windows OS **URL** field can be like this:
138
139 {{code}}
140 jdbc:h2:C:/Users/ ... /BlogTutorial
141 {{/code}}
142
143 //Notice, in the path, *nix like file separator "/" instead of Windows like// "\" (as you can read [[here>>url:http://www.h2database.com/html/faq.html||shape="rect"]]).
144
145
146
Pascal Robert 30.1 147 Now, right-click on **BlogModel** and select **New Entity**.
148
149 Type the following details in the **Basic** tab:
150
151 * **Name**: BlogEntry
152 * **Table Name**: BlogEntry
153 * **Class Name**: your.app.model.BlogEntry
154
155 Now, it's time to add the entity's attributes (aka, the table's columns). You will see that the entity already have an attributed named "id". That attribute is a integer for the primary key. Leave it there.
156
157 Let's create the first attribute: the title of the blog entry. Right-click on the entity and select **New Attribute**. Type the following values:
158
159 * **Name**: title
160 * **Column**: title
161 * **Prototype**: varchar255
162
163 When you use prototypes, you don't need to define the type (varchar, int, etc.) for the database, so by using prototypes, if you switch from a RDBMS system to another one, say from H2 to MySQL, you only need to change the JDBC connection string and bundle the EOF plugin for the RDBMS, no need to switch data types in the model.
164
165 Now, repeat the last two steps to create the other attributes for the **BlogEntry** entity, with the following values:
166
Filippo Laurìa 46.1 167 |=(((
168 Attribute name
169 )))|=(((
170 Column
171 )))|=(((
172 Prototype
173 )))
174 |(((
175 content
176 )))|(((
177 content
178 )))|(((
179 longtext
180 )))
181 |(((
182 creationDate
183 )))|(((
184 creationDate
185 )))|(((
186 dateTime
187 )))
188 |(((
189 lastModified
190 )))|(((
191 lastModified
192 )))|(((
193 dateTime
194 )))
Pascal Robert 30.1 195
196 If you did everything well, the list of attributes should look like this:
197
Filippo Laurìa 46.1 198 [[image:attach:list_wlock.png]]
199
pauldlynch 36.1 200 You will notice that the attributes have a column with a lock in it. When a lock is present, it will use the value of that attribute for //UPDATE ... WHERE attribute = ''// statement. This is to do optimistic locking, aka to prevent data conflict when the data object was modified by two different users. Using timestamps for optimistic locking is not a good idea because for certain RDBMS, the value can be different because of milliseconds, so remove the locks on the **creationDate** attribute. The final list should look like this:
Pascal Robert 30.1 201
Filippo Laurìa 46.1 202 [[image:attach:list.png]]
203
Pascal Robert 30.1 204 Next step is to create the **Author** entity. Create a new entity with **Author** at its name (and also as the table name), and for the class name, use **your.app.model.Author**. The attributes for this entity are:
205
Filippo Laurìa 46.1 206 |=(((
207 Attribute name
208 )))|=(((
209 Column
210 )))|=(((
211 Prototype
212 )))
213 |(((
214 firstName
215 )))|(((
216 firstName
217 )))|(((
218 varchar50
219 )))
220 |(((
221 lastName
222 )))|(((
223 lastName
224 )))|(((
225 varchar50
226 )))
227 |(((
228 email
229 )))|(((
230 email
231 )))|(((
232 varchar100
233 )))
Pascal Robert 30.1 234
235 Final list of attributes should look like this:
236
Filippo Laurìa 46.1 237 [[image:attach:author_list.png]]
238
pauldlynch 36.1 239 Now, it's time to link the two entities together. An Author can have multiple blog entries, and a BlogEntry can only have one author. To create the relationship (the join), right-click on **Author** and select **New Relationship**. On your right, select **BlogEntry** in the list. On your left, select **to many BlogEntries**, and on your right, select **to one Author**. Now, in BlogEntry, we need to store the primary key of the author so that we can make the join. The relationship builder allow us to add that attribute, so make sure **and a new foreign key named** is checked (it is checked by default). The **Create Relationship** pane should look like this:
Pascal Robert 30.1 240
Filippo Laurìa 46.1 241 [[image:attach:relationship.png]]
242
franc 34.1 243 If you check in the **Outline** tab, you should see that **Author** now have a **blogEntries** relationship, and **BlogEntry** have a **author** relationship.
Pascal Robert 30.1 244
Filippo Laurìa 46.1 245 [[image:attach:outline_tab.png]]
Pascal Robert 30.1 246
Filippo Laurìa 46.1 247 You are now ready to save the model. Save it (File -> Save) and close the **Entity Modeler** window. If you open the **Sources** in the main Eclipse window, you will notice that the **Sources** folder contains a package named **your.app.model**. (If this folder doesn't appear, you may need to set your preferences to automatically generate these source files; see the second suggestion on [[http:~~/~~/wiki.wocommunity.org/display/documentation/Useful+Eclipse+or+WOLips+Preferences>>url:http://wiki.wocommunity.org/display/documentation/Useful+Eclipse+or+WOLips+Preferences||rel="nofollow" shape="rect" class="external-link"]].)
Pascal Robert 30.1 248
Filippo Laurìa 46.1 249
250
251 That package have four Java classes: **_Author**, **Author**, **_BlogEntry** and **BlogEntry**. Those classes were generated by Veogen, a templating engine build on Velocity. The two classes that starts with a underscore are recreated every time you change the EOModel, so if you want to change something in those classes, you need to change the template (no need for that right now). But you can change freely the two classes that don't have the underscore, and this is what we will be doing.
252
253
254
Pascal Robert 30.1 255 What we are going to do is to write a simple method that returns the full name of an author, e.g. a method that simply concatenate the first name, a space and the last name of the author. To do so, double-click on **Author.java** and add the following methods:
256
257 {{code}}
franc 34.1 258 public String fullName() {
Pascal Robert 30.1 259 return this.firstName() + " " + this.lastName();
260 }
261
262 {{/code}}
263
franc 34.1 264 Nothing fancy here. Now open **BlogEntry.java** and add the following method:
Pascal Robert 30.1 265
franc 34.1 266 {{code}}
skcodes 44.1 267 @Override
franc 34.1 268 public void awakeFromInsertion(EOEditingContext editingContext) {
skcodes 44.1 269 super.awakeFromInsertion(editingContext);
270 NSTimestamp now = new NSTimestamp();
271 setCreationDate(now);
272 setLastModified(now);
franc 34.1 273 }
274
275 {{/code}}
276
skcodes 44.1 277 Why are we adding this? **awakeFromInsertion** is a very good way of setting default values when creating a new instance of a Enterprise Object (EO). In this case, we want to set automatically the creation and last modification dates without having the user to add those values.
franc 34.1 278
279 Now, let's use migrations to actually create the database.
280
281 == Using migrations ==
282
pauldlynch 36.1 283 Migrations allow you to create the tables and columns (and some types of constraint). **Entity Modeler** has support to generate the code for the first migration, which is called "migration 0". To do that, open the EOModel (**BlogModel EOModel** in the **Resources** folder), right-click on the model name and select **Generate Migration**.
franc 34.1 284
285 Copy the generated code in the clipboard. Close **Entity Modeler** and in the main Eclipse window, right-click on **Sources**, select **New** and select **Class**.
286
287 Type **your.app.model.migrations** as the package and **BlogModel0** as the name of the class. Click **Finish**.
288
289 In the **Sources** folder, open the **your.app.model.migrations** package, a class named **BlogModel0** should be there. Delete everything in that file **EXCEPT** the first line (which should be //package your.app.model.migrations//) and paste the code that was generated by **Entity Modeler**. Save the file.
290
291 One last step: migrations are disabled by default. To enable them, you need to uncomment two properties in the **Properties** file that is located in the **Resources** folder. Open that file (double-click on it).
292
293 Remove the pound char in front of those two properties:
294
295 {{code}}
296 #er.migration.migrateAtStartup=true
297 #er.migration.createTablesIfNecessary=true
298
299 {{/code}}
300
301 After removing the pound char, the two properties should look like this:
302
303 {{code}}
304 er.migration.migrateAtStartup=true
305 er.migration.createTablesIfNecessary=true
306
307 {{/code}}
308
Filippo Laurìa 46.1 309 You are now ready to start the application so that it creates the database! To do so, right-click on **Application.java** (in the **your.app** folder) and select **Run As** -> **WOApplication**. In Eclipse's Console tab, you should see some output, including something similar to:
franc 34.1 310
311 {{code}}
312 BlogRest[62990] INFO er.extensions.migration.ERXMigrator - Upgrading BlogModel to version 0 with migration 'your.app.model.migrations.BlogModel0@4743bf3d'
313 BlogRest[62990] INFO er.extensions.jdbc.ERXJDBCUtilities - Executing CREATE TABLE Author(email VARCHAR(100) NOT NULL, firstName VARCHAR(50) NOT NULL, id INTEGER NOT NULL, lastName VARCHAR(50) NOT NULL)
314 BlogRest[62990] INFO er.extensions.jdbc.ERXJDBCUtilities - Executing ALTER TABLE Author ADD PRIMARY KEY (id)
315 BlogRest[62990] INFO er.extensions.jdbc.ERXJDBCUtilities - Executing CREATE TABLE BlogEntry(authorID INTEGER NOT NULL, content TIMESTAMP NOT NULL, creationDate TIMESTAMP NOT NULL, id INTEGER NOT NULL, title VARCHAR(255) NOT NULL)
316 BlogRest[62990] INFO er.extensions.jdbc.ERXJDBCUtilities - Executing ALTER TABLE BlogEntry ADD PRIMARY KEY (id)
317 BlogRest[62990] INFO er.extensions.jdbc.ERXJDBCUtilities - Executing ALTER TABLE BlogEntry ADD CONSTRAINT "FOREIGN_KEY_BLOGENTRY_AUTHORID_AUTHOR_ID" FOREIGN KEY (authorID) REFERENCES Author (id)
318 BlogRest[62990] DEBUG NSLog - evaluateExpression: <er.h2.jdbcadaptor.ERH2PlugIn$H2Expression: "UPDATE _dbupdater SET version = ? WHERE modelname = ?" withBindings: 1:0(version), 2:"BlogModel"(modelName)>
319
320 {{/code}}
321
Filippo Laurìa 46.1 322 If you see this and that the application is running (it should open a window in your favorite browser), migration worked and your database have been created, congratulations! You can now stop the application (click the square red button in Eclipse's Console tab) and continue to the next step.
franc 34.1 323
Pascal Robert 30.1 324 = Creating REST controllers and routes =
franc 34.1 325
326 Project Wonder contains a framework called ERRest, which follow the same patterns as Ruby on Rails REST concepts. Using REST-style URLs is perfect for building a public blog and to create REST services to manage posting over HTTP with JSON, XML or other formats.
327
328 By default, a REST route in ERRest will generate a link like this:
329
330 {{code}}
331 /cgi-bin/WebObjects/AppName.woa/ra/EntityName/id
332 {{/code}}
333
334 So for our case, to get the first blog posting from BlogRest, the URL will look like this:
335
336 {{code}}
337 /cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries/1.html
338 {{/code}}
339
340 {{info}}
341 You can shorten the URL by using mod_rewrite in Apache httpd
342 {{/info}}
343
344 == Creating controllers ==
345
346 ERRest needs controllers to act as a broker between working with the objects and the routes. So let's create a controller for BlogEntry.
347
348 Create a Java class named **BlogEntryController**, in the **your.app.rest.controllers** package, that will extend from **er.rest.routes.ERXDefaultRouteController**. Click **Finish**.
349
350 When you extend from **ERXDefaultRouteController**, a bunch of methods are added to the subclass. Let's see what they are for.
351
352 * **updateAction**: to update a specific instance of BlogEntry
353 * **destroyAction**: to delete a specific instance of BlogEntry
354 * **showAction**: to get one specific instance of BlogEntry
355 * **createAction**: to create a new object (a new instance of BlogEntry)
356 * **indexAction**: to list all (or a sublist) of the objects.
357
358 {{info}}
Filippo Laurìa 46.1 359 In Project Wonder, **Action** at the end of a method is a convention for REST and Direct Actions, when you call those methods from certain components, you don't need to add the **Action** part.
franc 34.1 360 {{/info}}
361
Filippo Laurìa 46.1 362 For this tutorial, we will implement the **createAction** and **indexAction** methods. But first, we need to create a key filter. A key filter will... filter the input and the output of REST request so that you don't have to send all attributes for a blog entry. For example, we want to show the details for an author, but we don't want to show the password for the author (in real-life, the password would be encrypted)!
franc 34.1 363
364 Add this method in **BlogEntryController**:
365
366 {{code}}
367 protected ERXKeyFilter filter() {
368 ERXKeyFilter personFilter = ERXKeyFilter.filterWithAttributes();
369 personFilter.setAnonymousUpdateEnabled(true);
370
371 ERXKeyFilter filter = ERXKeyFilter.filterWithAttributes();
372 filter.include(BlogEntry.AUTHOR, personFilter);
373 filter.setUnknownKeyIgnored(true);
374
375 return filter;
376 }
377
378 {{/code}}
379
pauldlynch 36.1 380 Now, let's implement the **createAction** method:
franc 34.1 381
382 {{code}}
383 public WOActionResults createAction() throws Throwable {
384 BlogEntry entry = create(filter());
385 editingContext().saveChanges();
386 return response(entry, filter());
387 }
388
389 {{/code}}
390
391 In 3 lines of code, you can create an object based on the request, save the new object to the database and return the new object in the response. Not bad, eh?
392
pauldlynch 36.1 393 Last step in the controller: implementing the **indexAction** method. Again, the code is simple:
franc 34.1 394
395 {{code}}
396 public WOActionResults indexAction() throws Throwable {
397 NSArray<BlogEntry> entries = BlogEntry.fetchAllBlogEntries(editingContext());
398 return response(entries, filter());
399 }
400
401 {{/code}}
402
403 That code simply fetch all blog entries and return them in the response.
404
405 We can now go to the next step: adding the routes.
406
407 == Adding the routes ==
408
409 A route in ERRest is simply a way to define the URL for the entities and to specify which controller the route should use. When your controller extends from **ERXDefaultRouteController**, it's easy to register a controller and a route. In **Application.java**, in the **Application** constructor, add the following code:
410
411 {{code}}
412 ERXRouteRequestHandler restRequestHandler = new ERXRouteRequestHandler();
413 restRequestHandler.addDefaultRoutes(BlogEntry.ENTITY_NAME);
414 ERXRouteRequestHandler.register(restRequestHandler);
415 setDefaultRequestHandler(restRequestHandler);
416
417 {{/code}}
418
419 The **addDefaultRoutes** method do all of the required magic, and use convention. That's why we had to name the controller **BlogEntryController**, because the convention is <EntityName>Controller.
420
Filippo Laurìa 46.1 421 We are now reading to add and list blog postings! Start the application and take notice of the URL. It should be something like _[[http:~~/~~/yourip:someport/cgi-bin/WebObjects/BlogRest.woa_>>url:http://youripsomeport||shape="rect"]]
franc 34.1 422
423 == Adding posts and authors with curl ==
424
425 Since we didn't implement any HTML for our REST routes, we will create blog entries with //curl//, an open source HTTP client that is bundled with Mac OS X (you can use another client, like wget, if you like too). So let's create a blog entry.
426
Filippo Laurìa 46.1 427 To create a blog entry, you need to use the POST HTTP method. We will use JSON as the format since it's a bit less chatty than XML. So if the URL to the application is //[[http:~~/~~/192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa_>>url:http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa_||shape="rect"]], the full _curl// command will be:
franc 34.1 428
429 {{code}}
430 curl -X POST -v -d '{ "title": "First post", "content": "Some text", "author": { "firstName": "Pascal", "lastName": "Robert", "email": "probert@macti.ca" } }' http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.json
431 {{/code}}
432
433 The response should look this:
434
435 {{code}}
436 HTTP/1.0 201 Apple WebObjects
437 Content-Length: 249
438 x-webobjects-loadaverage: 0
439 Content-Type: application/json
440
441 {"id":1,"type":"BlogEntry","content":"Some text","creationDate":"2011-12-27T21:59:08Z","title":"First post","author":{"id":1,"type":"Author","email":"probert@macti.ca","firstName":"Pascal","lastName":"Robert"}}
442
443 {{/code}}
444
445 To get a list of blog entries:
446
447 {{code}}
448 curl -X GET http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.json
449
450 {{/code}}
451
452 You can stop the application and proceed to the next step.
453
454 == Adding HTML views for blog posts ==
455
456 Now, let's build a HTML view for blog posts (you don't want your readers to get your posts by JSON, right?). Again, we will use convention to make it work easily. Open up **BlogEntryController** and add the following method:
457
458 {{code}}
459 @Override
460 protected boolean isAutomaticHtmlRoutingEnabled() {
461 return true;
462 }
463
464 {{/code}}
465
Filippo Laurìa 46.1 466 Switching the return value of this method says that we will follow a certain convention for HTML components. The convention for automatic HTML routing is that the component should be named <EntityName><Action>Page.wo. So in our case, the component will be **BlogEntryIndexPage**. Right-click on the project name in Eclipse and select **New** -> **WOComponent**. Change the name to **BlogEntryIndexPage** and check the **Create HTML contents** button. Click **Finish**.
franc 34.1 467
pauldlynch 36.1 468 The next step to get it to work is to make **BlogEntryIndexPage** to implement the **er.rest.routes.IERXRouteComponent** interface.
franc 34.1 469
470 {{code}}
471 import er.rest.routes.IERXRouteComponent;
472
473 public class BlogEntryIndexPage extends WOComponent implements IERXRouteComponent {
474
475 {{/code}}
476
477 So now, the automatic HTML routing will send the request for **ra/blogEntries.html** to the **BlogEntryIndexPage** component. But we don't have any content in this component, so let's make a method to fetch all blog entries per creation date in descending order. So in **BlogEntryIndexPage.java**, add the following method:
478
479 {{code}}
480 public NSArray<BlogEntry> entries() {
481 EOEditingContext ec = ERXEC.newEditingContext();
482 return BlogEntry.fetchAllBlogEntries(ec, BlogEntry.CREATION_DATE.descs());
483 }
484
485 {{/code}}
486
487 We need to use that method in a WORepetition, and for that loop, we need a BlogEntry variable to iterate in the list, so add the following code to **BlogEntryIndexPage.java**:
488
489 {{code}}
490 private BlogEntry entryItem;
491
492 public BlogEntry entryItem() {
493 return entryItem;
494 }
495
496 public void setEntryItem(BlogEntry entryItem) {
497 this.entryItem = entryItem;
498 }
499
500 {{/code}}
501
502 The Java part is done, so let's add the loop inside the component. Open **BlogEntryIndexPage.wo** (it's located in the **Component** folder) and right after the <body> tag, add:
503
504 {{code}}
505 <wo:loop list="$entries" item="$entryItem">
506 <p><wo:str value="$entryItem.title" /></p>
507 <p><wo:str value="$entryItem.author.fullName" /></p>
508 </wo:loop>
509
510 {{/code}}
511
512 That component code will loop over the blog entries and display the title of the entry + the name of the author. Save everything and run the application.
513
Filippo Laurìa 46.1 514 If you go to [[http:~~/~~/192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.html>>url:http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.html||shape="rect"]], you will see the list of blog entries!
franc 34.1 515
516 Now that we have a list of blog entries, let's make a page to show the content of a blog entry. Create a new component named **BlogEntryShowPage**.
517
Filippo Laurìa 46.1 518 Open **BlogEntryShowPage.java** and make sure the class implements **er.rest.routes.IERXRouteComponent**.
franc 34.1 519
520 {{code}}
521 import er.rest.routes.IERXRouteComponent;
522
523 public class BlogEntryShowPage extends WOComponent implements IERXRouteComponent {
524
525 {{/code}}
526
527 We need to add other methods to receive the BlogEntry object from the controller. In **BlogEntryShowPage.java**, add:
528
529 {{code}}
530 private BlogEntry blogEntry;
531
532 @ERXRouteParameter
533 public void setBlogEntry(BlogEntry blogEntryFromController) {
534 this.blogEntry = blogEntryFromController;
535 }
536
537 public BlogEntry blogEntry() {
538 return this.blogEntry;
539 }
540
541 {{/code}}
542
543 The **@ERXRouteParameter** annotation tells the REST framework that it can automatically receive an object from the controller. And again, it's convention at work. You have to use the annotation and the setter name should be //set<EntityName>//, so for a BlogEntry, it's //setBlogEntry//, for a Author, it will be //setAuthor//.
544
545 The Java part of the work is done, so save the Java class. It's time to work on the component part. Open **BlogEntryShowPage.wo** and between the <body></body> part, add:
546
547 {{code}}
548 <h1><wo:str value="$blogEntry.title" /></h1>
549 <p><wo:str value="$blogEntry.content" /></p>
550 <p>Created on: <wo:str value="$blogEntry.creationDate" dateformat="%Y/%m/%d" /></p>
551 <p>Added by: <wo:str value="$blogEntry.author.fullName" /></p>
552
553 {{/code}}
554
555 Our view component is done, the only thing remaining is a link for the blog entry list (BlogEntryIndexPage) to the view page (BlogEntryShowPage). Save **BlogEntryShowPage.wo** and open **BlogEntryIndexPage.wo**. We are going to add a link on the title, you will replace to replace this:
556
557 {{code}}
558 <p><wo:str value="$entryItem.title" /></p>
559
560 {{/code}}
561
562 with:
563
564 {{code}}
565 <p><wo:ERXRouteLink entityName="BlogEntry" record="$entryItem" action="show"><wo:str value="$entryItem.title" /></wo:ERXRouteLink></p>
566
567 {{/code}}
568
Filippo Laurìa 46.1 569 Save the component and run the app. Go to [[http:~~/~~/192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.html>>url:http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.html||shape="rect"]] to get the list of posts, and you should see a link on the title. Click on it, and now you get the full details of the blog entry!
franc 34.1 570
Filippo Laurìa 46.1 571 The REST part of this tutorial is now complete, [[you can now move to the next part of the tutorial>>doc:Your First Framework]].