Create Initial Display of Registration Screen

This chapter describes the initial display of the registration screen.

Create a JSP for the registration screen

Place the template JSP under /src/main/webapp/WEB-INF/view/client.

Implement the part that is initially displayed on the screen.

Add the content of the registration screen to create.jsp.

    <div class="form-group label-static is-empty">
        <label class="control-label"> Client name</label>
        <!-- Client name text box -->
        <!-- Since the form has not been created, specify a temporary value for the name attribute -->
        <n:text name="tmp" cssClass="form-control input-text"/>
    <div class="form-group label-static is-empty">
        <label class="control-label">Industry type</label>
        <!-- Pull down of industry type -->
        <!-- Since the form has not been created, specify a temporary value for the name attribute -->
                cssClass="btn dropdown-toggle"/>
    <div class="button-nav">
        <!-- Registration button -->
        <!-- Since the registration confirmation screen is not yet created, specify a temporary value for the uri attribute -->
                cssClass="btn btn-raised btn-success">Registration</n:button>
Key points of this implementation
Create an initial display method for a business action

Add a business action method to ClientAction that performs the following process.

  • Acquire the data to be displayed in the pull-down and register it in the request scope.
  • Forward to the JSP of the initial display screen.
public HttpResponse input(HttpRequest request, ExecutionContext context) {
    EntityList<Industry> industries = UniversalDao.findAll(Industry.class);
    context.setRequestScopedVar("industries", industries);
    return new HttpResponse("/WEB-INF/view/client/create.jsp");

The signature of the business action method should be as follows. A 404 error occurs if the business action method does not meet the following signature.

public HttpResponse methodName(HttpRequest request, ExecutionContext context)
  • request – request object passed from the framework
  • context – execution context passed from the framework
  • return – response object with transition destination
Key points of this implementation
  • To display the pull down of industry type on the registration screen, use Universal DAO to acquire all the industry type information from the database.
  • To pass a value to a JSP, register the acquired industry type list in the request scope.
Map URLs and business actions

The mapping process is performed using the OSS library http_request_router(external site) . Add configuration for mapping the specified URL and initial display process.

  <!-- Set it before other mappings because it will be evaluated from above -->
  <get path="/action/client" to="Client#input"/>
  <!-- Other settings are omitted -->


For instructions on how to specify routes.xml, see Library README document (external site) .

Create a link to the registration screen

Create a link to the client registration screen in the header menu.

<ul class="nav navbar-nav">
  <!-- Other links are omitted -->
    <n:a href="/action/client"> Client registration</n:a>
Key points of this implementation
Communication confirmation

Confirm communications with the following procedure.

  1. Log in to the application and confirm that the “Client Registration”(顧客登録) link has been created in the header menu.
  1. Confirm that it transitions to the client registration screen on clicking the Client Registration link, and the “Client Name”(顧客名) form, the “Industry type”(業種) pull-down, and the registration button are displayed.
  1. Confirm if the “Industry type”(業種) pull-down can be selected.