Skip to content

phase 4

Jump to bottom
Pedro Felix edited this page May 25, 2020 · 3 revisions

Phase 4

Introduction

This document describes the requirements for the fourth and final phase of the Software Laboratory project.

Requirements

Using PostgreSQL

Use the PostgreSQL Relational Database Management System, instead of SQL Server.

  • Install PostgreSQL on the development machines. Alternatively, use a docker image (see build.gradle).
  • Obtain and use a JDBC driver for PostgreSQL.
  • Change both the DDL and DML statements to use the PostgreSQL dialect.
  • Use the JDBC_DATABASE_URL environment variable to configure the PostgreSQL connection settings.

Hosting on Heroku

Host the application on the Heroku.

  • Create an Heroku free account. Heroku is an example of a Platform-as-a-Service (PaaS) provider.
  • Install the Heroku CLI (Command Line Interface) on all the development machines.
  • On the Heroku web site, create a new application
    • The name should follow the following structure:isel-ls-1920-2-g<número-do-grupo>.
    • Select the "Europe" region.
  • On the application home page, provision the "Heroku Postgres" add-on using the "Hobby Dev - Free" plan.
    • The JDBC_DATABASE_URL environment variable will be automatically added to Java the execution environment.
  • Create the Procfile file with web: followed up by the necessary to start the application.
  • On the command line, do heroku login.
  • On the command line, inside the project root folder, do heroku git:remote -a isel-ls-1920-2-gXX. This will create a Git remote pointing to the Heroku repository.

Resource creation via the HTTP interface

The main goal for this requirement is to add support for the commands with POST method in the HTTP interface. For that, the following changes should be made.

  • Resource /rooms/create, allowing the following methods:

    • GET method - returns a representation with a creation HTML form.
    • POST method - creates a new room. When successful, redirects to the room detail. If an error occurs, returns creation HTML form with error information.

  • Resources /rooms/{rid}/bookings/create, allowing the following methods:

    • GET method - returns a representation with a creation HTML form.
    • POST method - creates a new booking. When successful, redirects to the booking detail. If an error occurs, returns creation HTML form with error information.

  • Resource /users/create, with a similar behaviour.

  • Resource /labels/create, with a similar behavior.

Each one of these forms must, when submitted, send a POST request to the associated resource path. For instance:

  • The representation returned on a GET /rooms/create request should contain a form with all the fields required to create a room.
  • This form, when submitted, must send a POST request to /rooms/create containing these fields in the body.
  • If the POST request is successful, i.e. a new room was created, its response should be a 303 See Other with the Location header pointing to the created room (e.g. /rooms/1). Otherwise, it should be a form with added error information.

Dependency management

For this last phase, the project should stop relying on locally stored vendor JARs and use the Gradle supported dependency management system.

Delivery

The completed project must be delivery until June 20 (end of week 16), via the creation of a 1.0.0 tag on the GitHub repository. The final project evaluations will start on June 22.

Clone this wiki locally