Working with Pages and Classes

In most cases, when you work with Pages and Classes, you want to separate the code that handles the user interface from the code that handles the data. In the platform, you do this by following the Model-View-Controller design pattern and creating two classes and a page.

Learn More:

• MVC (Model-View-Controller)
• Pages and Classes Example
• Governors on Java Code

How it Works

This section describes how a request flows from a page to the controller to the worker and how the result is displayed in the page.

Note: The code samples are presented here for illustration, and should not be used to build actual pages or classes. See Practical Example below for more on working code samples.

In this example, a page displays a search form for Directory object which is a built-in Object available to every account. The user can select the criteria to search the directory entries and then enter the string to search for.

<form name="mainForm" action="/networking/controller/com/platform/demo/samples/DirectoryController" method="POST">
  <input type="hidden" name="action" value="search" />
  <table>
      <tr>
          <!-- ... -->
          <td>Search</td>
          <td>
              <select name="searchType">
                  <option value="first_name">First Name</option>
                  <option value="name1">Last Name</option>
                  <option value="address">Address</option>
                  <!-- ... -->
              </select>
          </td>
          <td> for </td>
          <td><input type="text" name="searchString" value="<%=searchString%>" 
              />
          </td>
          <td><input type="submit" name="submit" value="Search" /></td>
      </tr>
  </table>
</form>

The action attribute of the <form> tag specifies the URL of the class that you wrote that implements the Controller interface (DirectoryController in this example).

When the user clicks the Search button, the form is submitted to the DirectoryController's execute method, shown below.

execute Method

import com.platform.api.*;

import java.util.HashMap;

public class DirectoryController implements Controller
{

  public ControllerResponse execute(HashMap params) throws Exception
  {
    String action = (String)params.get("action");
    
    // ...

    ControllerResponse cr = new ControllerResponse();
    Directory directory = new Directory();
    Result result = null;

    if(action.equals("search"))
    {
      result = directory.search(params);
      cr.setTargetPage("directory.jsp");
    }
    // ...
    params.put("opResult", result);
    // ...
    cr.setData(params);
    return cr;
  }
}

This code:

• Gets the value of the action key passed in params
• Creates instances of the predefined classes ControllerResponse and Result
• Creates an instance of the worker class Directory (shown below)
• Calls the search method (shown below) in the worker class, if the action is "search", passing it params; also sets the next JSP name
• Puts the result of the method call in params using the key opResult
• Calls the setData method in ControllerResponse, specifying params as the argument
• Returns the instance of ControllerResponse

search Method

Here is the search method in the Directory worker class.

import com.platform.api.*;


public class Directory
{
  // ...
  public Result search(HashMap params) throws Exception
  {
        Parameters addParams = Functions.getParametersInstance();
        addParams.add(params);

        String searchType = (String)params.get("searchType");
        String searchString = (String)params.get("searchString");

        Result result = null;
        if(searchType != null && !searchType.equals(""))
        {
          // Get the object ID from the GUI, by inspecting the object
          String directory_object_id = "361077714ltd1991022913";
          result = 
            Functions.searchRecords(directory_object_id,
                "record_id,first_name,address,city,state,zip,direct_phone,email",
                searchType + " contains '" + searchString + "'");
        }
        return result;
  }
  // ...
}

This code:

• Creates an instance of Parameters and adds params to it
• Gets the values of the searchType and searchString keys from params
• Creates an instance of Result
• Calls searchRecords, passing in the searchType and searchString and setting the Result object with the returned value
• Returns the Result object

Displaying the Results

So, the search request originated in the page, went to the controller, and finally to the worker. Now we look at how the search results get displayed in the page.

This example:

• Gets the opResult value from params and puts it into result
• Iterates through result, creating a table row for each set of data

In the Page, here is the code that gets the search results:

<%
  java.util.HashMap params = (java.util.HashMap)controllerResponse.getData();

  String searchType = params.get("searchType") == null ? "" : (String) params.get("searchType");
  String searchString = params.get("searchString") == null ? "" : (String) params.get("searchString");
  String message = params.get("message") == null ? "" : (String) params.get("message");
%>

The HTML and code below puts the search results into table rows.

<%
Result result = (Result)params.get("opResult");
if(result != null)
{
%>
<table>
    <tr>
        <td colspan="5">Search Results:</td>
    </tr>
    <!-- ... -->        
    <%
    ParametersIterator iter = result.getIterator();
    while(iter.hasNext())
    {
        Parameters row = iter.next();
    %>
    <tr>
        <!-- ... -->
        <td><%=row.get("first_name")%></td>
        <td><%=row.get("address")%></td>
        <!-- ... -->
    </tr>
    <%
    }
}
    %>
</table>

Practical Example

JSP Pages are used to develop the UI to suit any custom requirements in an organization. The logic on how to perform the various operations on the server is present in the classes (Java code).

To try out the concepts of Pages and Classes, follow this tutorial to add real code to platform elements and build a .jsp page that can be used in a web browser.

This example describes how to use a Page to perform the following actions on records in the Directory object:

• search for records based on specified criteria
• add records
• update records

Considerations

It is important to create the Classes files first, then create the Pages. Five files are provided, including two Classes, and three Pages. The files should be created in this order:

1. Class Directory.java
2. Class DirectoryController.java
3. Page AddUpdate.jsp
4. Page Directory.jsp
5. Page SearchPage.jsp

To add the Pages and Classes:

1. To create the (.java) Java pages, follow the instructions at Add a Class

   Create the class Directory.java from: Directory.java

   • Copy and paste the contents into the Class
   • Save the file as Directory.java

   Create the class DirectoryController.java from: DirectoryController.java

   • Copy and paste the contents into the Class
   • Save the file as DirectoryController.java

2. To create the (.jsp) Java Server Pages, follow the instructions at Add a Page

   Create the page AddUpdate.jsp from: AddUpdate.jsp

   • Copy and paste the contents into the Page
   • Save the file as AddUpdate.jsp

   Create the page Directory.jsp from: Directory.jsp

   • Copy and paste the contents into the Page
   • Save the file as Directory.jsp

   Create the page SearchPage.jsp from: SearchPage.jsp

   • Copy and paste the contents into the Page
   • Save the file as SearchPage.jsp

3. To invoke the Directory page from the URL, copy and paste the following into a web browser. A valid username and password is required to log in to the platform.

https://www.longjump.com/networking/pages/Directory.jsp

After logging in, the user can perform these actions in the Directory object:

• search for records based on specified criteria
• add records
• update records

MVC

MVC: Model-View-Controller

• A worker class that retrieves, updates, and deletes data (the Model)
• A page that handles the user interface (the View)
• A class that creates an instance of the worker class, call its methods, and sets the next page to display (the Controller)

The controller is a special class that implements the Controller interface. The Controller interface requires you to implement the execute method: ControllerResponse execute(HashMap params) This method returns an instance of the ControllerResponse class. The platform uses the ControllerResponse class to send the appropriate response to the browser. The argument params in the execute method contains the POST and GET data in the HTTP Request. If an HTML form is being submitted to the controller, the params HashMap contains all the <input> fields in the page. For each field: The key of params is the name attribute of the <input> tag The value of params is the value attribute of the <input> tag Call these ControllerResponse methods to set the return value of the execute method: setData: set the data to be made available to the next page setTargetPage: set the name of the next page to display In the controller, you create an instance of a worker class and call its methods to perform operations. For details, see Controller Interface and ControllerResponse Class. In a page, you have an implicit object called controllerResponse: You call its getData method to get the data that was set by the controller You can set any Java object in controllerResponse by calling its setData method