Changes for page Your First Rest Project

Last modified by Steve Peery on 2013/09/06 11:02

From 10.1 to 11.1 From 19.1 to 20.1

From version 11.1

edited by Pascal Robert
on 2011/12/27 22:21

Change comment: There is no comment for this version

To version 19.1

edited by skcodes
on 2013/05/13 12:53

Change comment: Migrated to Confluence 4.0

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.probert
++XWiki.skcodes

Content

@@ -1,4 +1,4 @@
--{{toc}}{{/toc}}
++{{toc/}}
  = Introduction =
@@ -20,20 +20,93 @@
  BlogEntry will have the following columns:
--|= Column name |= Type |= Constraints
--| id | integer | primary key
--| title | string(255) |
--| content | string(4000) |
--| creationDate | timestamp |
--| author | integer | relation with Author
++|=(((
++Column name
++)))|=(((
++Type
++)))|=(((
++Constraints
++)))
++|(((
++id
++)))|(((
++integer
++)))|(((
++primary key
++)))
++|(((
++title
++)))|(((
++string(255)
++)))|(((
++
++)))
++|(((
++content
++)))|(((
++string(4000)
++)))|(((
++
++)))
++|(((
++creationDate
++)))|(((
++timestamp
++)))|(((
++
++)))
++|(((
++lastModified
++)))|(((
++timestamp
++)))|(((
++
++)))
++|(((
++author
++)))|(((
++integer
++)))|(((
++relation with Author
++)))
  Author will have the following columns:
--|= Column name |= Type |= Constraints
--| id | integer | primary key
--| firstName | string(50) |
--| lastName | string(50) |
--| email | string(100) | unique
++|=(((
++Column name
++)))|=(((
++Type
++)))|=(((
++Constraints
++)))
++|(((
++id
++)))|(((
++integer
++)))|(((
++primary key
++)))
++|(((
++firstName
++)))|(((
++string(50)
++)))|(((
++
++)))
++|(((
++lastName
++)))|(((
++string(50)
++)))|(((
++
++)))
++|(((
++email
++)))|(((
++string(100)
++)))|(((
++unique
++)))
  == Creating the EOModel ==
@@ -41,7 +41,7 @@
  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.
--To create the EOModel, in the project right-click on the project name and select **New** > **EOModel**.
++To create the EOModel, in the project right-click on the project name and select **New** -> **EOModel**.
  Name it **BlogModel** and in the plugin list, select **H2**. Click **Finish**.
@@ -49,8 +49,14 @@
  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.
--In the Entity Modeler window, click on **Default**, and for the **URL** field, type {{code}}jdbc:h2:~/BlogTutorial{{/code}}. When the database will be created, it will be stored in your home directory (/Users/youruser/ on OS X).
++In the Entity Modeler window, click on **Default**, and for the **URL** field, type
++{{code}}
++jdbc:h2:~/BlogTutorial
++{{/code}}
++
++. When the database will be created, it will be stored in your home directory (/Users/youruser/ on OS X).
++
  Now, right-click on **BlogModel** and select **New Entity**.
  Type the following details in the **Basic** tab:
@@ -71,30 +71,79 @@
  Now, repeat the last two steps to create the other attributes for the **BlogEntry** entity, with the following values:
--|= Attribute name |= Column |= Prototype
--| content | content | longtext
--| creationDate | creationDate | dateTime
++|=(((
++Attribute name
++)))|=(((
++Column
++)))|=(((
++Prototype
++)))
++|(((
++content
++)))|(((
++content
++)))|(((
++longtext
++)))
++|(((
++creationDate
++)))|(((
++creationDate
++)))|(((
++dateTime
++)))
++|(((
++lastModified
++)))|(((
++lastModified
++)))|(((
++dateTime
++)))
  If you did everything well, the list of attributes should look like this:
--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 **lastModified** and **creationDate** attributes. The final list should look like this:
++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:
  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:
--|= Attribute name |= Column |= Prototype
--| firstName | firstName | varchar50
--| lastName | lastName | varchar50
--| email | email | varchar100
++|=(((
++Attribute name
++)))|=(((
++Column
++)))|=(((
++Prototype
++)))
++|(((
++firstName
++)))|(((
++firstName
++)))|(((
++varchar50
++)))
++|(((
++lastName
++)))|(((
++lastName
++)))|(((
++varchar50
++)))
++|(((
++email
++)))|(((
++email
++)))|(((
++varchar100
++)))
  Final list of attributes should look like this:
--Now, it's time to link the two entities together. A 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 left, 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:
++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:
  If you check in the **Outline** tab, you should see that **Author** now have a **blogEntries** relationship, and **BlogEntry** have a **author** relationship.
--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**.
++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"]].)
--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.
++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.
  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:
@@ -112,19 +112,21 @@
  	@Override
  	public void awakeFromInsertion(EOEditingContext editingContext) {
--	  super.awakeFromInsertion(editingContext);
--	  this.setCreationDate(new NSTimestamp());
++		super.awakeFromInsertion(editingContext);
++		NSTimestamp now = new NSTimestamp();
++		setCreationDate(now);
++		setLastModified(now);
  	}
  {{/code}}
--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 date without having the user to add that value.
++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.
  Now, let's use migrations to actually create the database.
  == Using migrations ==
--Migrations allow you to create the tables and columns (and some types of constraint). **Entity Modeler** have 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**.
++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**.
  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**.
@@ -152,7 +152,7 @@
  {{/code}}
--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:
++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:
  {{code}}
@@ -166,7 +166,7 @@
  {{/code}}
--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.
++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.
  = Creating REST controllers and routes =
@@ -188,8 +188,6 @@
  You can shorten the URL by using mod_rewrite in Apache httpd
  {{/info}}
--.
--
  == Creating controllers ==
  ERRest needs controllers to act as a broker between working with the objects and the routes. So let's create a controller for BlogEntry.
@@ -205,16 +205,16 @@
  * **indexAction**: to list all (or a sublist) of the objects.
  {{info}}
--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.
++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.
  {{/info}}
--For this tutorial, we will implement the **createAction** and **showAction** 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)!
++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)!
  Add this method in **BlogEntryController**:
  {{code}}
--  protected ERXKeyFilter filter() {
++protected ERXKeyFilter filter() {
      ERXKeyFilter personFilter = ERXKeyFilter.filterWithAttributes();
      personFilter.setAnonymousUpdateEnabled(true);
@@ -227,11 +227,11 @@
  {{/code}}
--Now, let's implement the **creationAction** method:
++Now, let's implement the **createAction** method:
  {{code}}
--  public WOActionResults createAction() throws Throwable {
++public WOActionResults createAction() throws Throwable {
      BlogEntry entry = create(filter());
      editingContext().saveChanges();
      return response(entry, filter());
@@ -241,11 +241,11 @@
  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?
--Last step in the controller: implementing the **showAction** method. Again, the code is simple:
++Last step in the controller: implementing the **indexAction** method. Again, the code is simple:
  {{code}}
--  public WOActionResults indexAction() throws Throwable {
++public WOActionResults indexAction() throws Throwable {
      NSArray<BlogEntry> entries = BlogEntry.fetchAllBlogEntries(editingContext());
      return response(entries, filter());
    }
@@ -262,7 +262,7 @@
  {{code}}
--    ERXRouteRequestHandler restRequestHandler = new ERXRouteRequestHandler();
++ERXRouteRequestHandler restRequestHandler = new ERXRouteRequestHandler();
      restRequestHandler.addDefaultRoutes(BlogEntry.ENTITY_NAME);
      ERXRouteRequestHandler.register(restRequestHandler);
      setDefaultRequestHandler(restRequestHandler);
@@ -269,15 +269,15 @@
  {{/code}}
--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.
++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.
--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//
++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://yourip:someport/cgi-bin/WebObjects/BlogRest.woa_||shape="rect"]]
  == Adding posts and authors with curl ==
  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.
--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_, the full //curl// command will be~://
++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:
  {{code}}
  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
@@ -304,4 +304,133 @@
  {{/code}}
++You can stop the application and proceed to the next step.
++
  == Adding HTML views for blog posts ==
++
++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:
++
++{{code}}
++
++@Override
++  protected boolean isAutomaticHtmlRoutingEnabled() {
++    return true;
++  }
++
++{{/code}}
++
++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**.
++
++The next step to get it to work is to make **BlogEntryIndexPage** to implement the **er.rest.routes.IERXRouteComponent** interface.
++
++{{code}}
++
++import er.rest.routes.IERXRouteComponent;
++
++public class BlogEntryIndexPage extends WOComponent implements IERXRouteComponent {
++
++{{/code}}
++
++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:
++
++{{code}}
++
++public NSArray<BlogEntry> entries() {
++      EOEditingContext ec = ERXEC.newEditingContext();
++      return BlogEntry.fetchAllBlogEntries(ec, BlogEntry.CREATION_DATE.descs());
++    }
++
++{{/code}}
++
++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**:
++
++{{code}}
++
++private BlogEntry entryItem;
++
++    public BlogEntry entryItem() {
++      return entryItem;
++    }
++
++    public void setEntryItem(BlogEntry entryItem) {
++      this.entryItem = entryItem;
++    }
++
++{{/code}}
++
++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:
++
++{{code}}
++
++<wo:loop list="$entries" item="$entryItem">
++      <p><wo:str value="$entryItem.title" /></p>
++      <p><wo:str value="$entryItem.author.fullName" /></p>
++    </wo:loop>
++
++{{/code}}
++
++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.
++
++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!
++
++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**.
++
++Open **BlogEntryShowPage.java** and make sure the class implements **er.rest.routes.IERXRouteComponent**.
++
++{{code}}
++
++import er.rest.routes.IERXRouteComponent;
++
++public class BlogEntryShowPage extends WOComponent implements IERXRouteComponent {
++
++{{/code}}
++
++We need to add other methods to receive the BlogEntry object from the controller. In **BlogEntryShowPage.java**, add:
++
++{{code}}
++
++private BlogEntry blogEntry;
++
++    @ERXRouteParameter
++    public void setBlogEntry(BlogEntry blogEntryFromController) {
++      this.blogEntry = blogEntryFromController;
++    }
++
++    public BlogEntry blogEntry() {
++      return this.blogEntry;
++    }
++
++{{/code}}
++
++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//.
++
++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:
++
++{{code}}
++
++<h1><wo:str value="$blogEntry.title" /></h1>
++    <p><wo:str value="$blogEntry.content" /></p>
++    <p>Created on: <wo:str value="$blogEntry.creationDate" dateformat="%Y/%m/%d" /></p>
++    <p>Added by: <wo:str value="$blogEntry.author.fullName" /></p>
++
++{{/code}}
++
++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:
++
++{{code}}
++
++<p><wo:str value="$entryItem.title" /></p>
++
++{{/code}}
++
++with:
++
++{{code}}
++
++<p><wo:ERXRouteLink entityName="BlogEntry" record="$entryItem" action="show"><wo:str value="$entryItem.title" /></wo:ERXRouteLink></p>
++
++{{/code}}
++
++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!
++
++The REST part of this tutorial is now complete, [[you can now move to the next part of the tutorial>>doc:Your First Framework]].

Changes for page Your First Rest Project

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?