Changes for page Your First Rest Project

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

From 30.1 to 31.1 From 36.1 to 37.1

From version 31.1

edited by Pascal Robert
on 2011/12/27 23:07

Change comment: There is no comment for this version

To version 36.1

edited by pauldlynch
on 2012/05/28 04:09

Change comment: Minor spelling, and make method names in text match code.

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -77,7 +77,7 @@
  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:
@@ -88,7 +88,7 @@
  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.
@@ -124,7 +124,7 @@
  == 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**.
@@ -206,7 +206,7 @@
  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**:
@@ -225,7 +225,7 @@
  {{/code}}
--Now, let's implement the **creationAction** method:
++Now, let's implement the **createAction** method:
  {{code}}
@@ -239,7 +239,7 @@
  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}}
@@ -310,7 +310,7 @@
  {{code}}
--  @Override
++@Override
    protected boolean isAutomaticHtmlRoutingEnabled() {
      return true;
    }
@@ -317,9 +317,9 @@
  {{/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**.
++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 implements the **er.rest.routes.IERXRouteComponent** interface.
++The next step to get it to work is to make **BlogEntryIndexPage** to implement the **er.rest.routes.IERXRouteComponent** interface.
  {{code}}
@@ -333,7 +333,7 @@
  {{code}}
--    public NSArray<BlogEntry> entries() {
++public NSArray<BlogEntry> entries() {
        EOEditingContext ec = ERXEC.newEditingContext();
        return BlogEntry.fetchAllBlogEntries(ec, BlogEntry.CREATION_DATE.descs());
      }
@@ -344,12 +344,12 @@
  {{code}}
--    private BlogEntry entryItem;
++private BlogEntry entryItem;
      public BlogEntry entryItem() {
        return entryItem;
      }
--
++
      public void setEntryItem(BlogEntry entryItem) {
        this.entryItem = entryItem;
      }
@@ -360,7 +360,7 @@
  {{code}}
--    <wo:loop list="$entries" item="$entryItem">
++<wo:loop list="$entries" item="$entryItem">
        <p><wo:str value="$entryItem.title" /></p>
        <p><wo:str value="$entryItem.author.fullName" /></p>
      </wo:loop>
@@ -369,4 +369,66 @@
  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_, you will see the list of blog entries!//
++If you go to [[http://192.168.0.102:52406/cgi-bin/WebObjects/BlogRest.woa/ra/blogEntries.html]], 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&nbsp;**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]] 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 switch to the next part of the tutorial.

Changes for page Your First Rest Project

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?