Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Default error handling setup and automatic GSP page matching without requiring controller actions

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 grails-app
Octocat-spinner-32 scripts
Octocat-spinner-32 src
Octocat-spinner-32 .classpath
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .project
Octocat-spinner-32 ErrorsGrailsPlugin.groovy
Octocat-spinner-32 README.md
Octocat-spinner-32 application.properties
README.md

Grails Errors Plugin

This plugin sets up some basic error handling for your application, namely 403, 404 and 500 errors. Specifically, it creates a default controller for handling 403, 404 and 500 status codes, along with accompanying GSPs. Simply install, and it will prompt for a name for the controller to handle these errors.

You can skip adding the errors controller on install and add it later instead by executing

> grails generate-errors-controller xyz.ErrorsController

In addition, before rendering a 404, it will look for .gsp pages in the grails-app/view folder matching the Grails convention. This allows .gsp pages to be added without creating controllers or further configuration of the URL mappings. This is useful in allowing GSP pages to be added to your project by people not familiar with Groovy/Grails.

For example, adding the file grails-app/view/company/aboutus.gsp will cause it be rendered for a request to /company/aboutus without further configuration.

Something went wrong with that request. Please try again.