Skip to content

Overview

Concepts and Principles

Development

Overview

IDEs

API Explorer

Releases

Release Notes

TORO Integrate

Coder Studio

Coder Cloud

Bug Reports

Search

Using a Gloop Service to Render a JSP Page

Introduction

TORO Integrate supports the creation and mapping of web pages the Spring way. But instead of Groovy code, did you know you could use Gloop to create your controller and populate your page with your models1?

The examples package includes a sample service, API, and JSP page to show how you could map and render a JSP page using Gloop.

Related articles

Please see the following articles for more information:

Try It!

To see the JSP page live: ensure that the examples package is started and then visit <host>:<port>/api/jspResponse/page2 on your browser.

There, you will see a form. Fill up the form and submit to see data get rendered. You will notice that upon submission, the data you entered will be visible below the form.

The page after submission

To see the files related to this example (and play around with the results), expand the examples package entry under the Coder Navigator and navigate to the code folder. Afterwards, look for the jspResponse package. This package contains API file that defines the controller and the Gloop service which is responsible for mapping the values to be shown in the view:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
examples
├── ...
├── code
│   ├── ...
│   ├── jspResponse
│   │   ├── api
│   │   │   └── JspController.api
│   │   └── SendJspPage.gloop
│   ├── ...
├── ...

In addition to this, the JSP page, named sample.jsp, is visible in the example package's web directory.

How It Works...

To serve web content via Spring and Gloop, here are the steps you should follow:

  1. Put your JSP file under your package's web directory.
  2. Create a Gloop service with an output variable named $gloopView.
  3. Set the $gloopView variable's value so that it is equal to the basename3 (extension-excluded filename) of the JSP file.

  1. See also: the MVC pattern

  2. <host> and <port> must be substituted with values that depend on the configuration of your own server. 

  3. Although in general, what you should return also depends on the requirements of the configured ViewResolver