Visualising Web Archive via Solr - Grails Framework version

A powerful Groovy-based web application framework for the JVM built on top of Spring Boot.

• assets – a place where we store static assets files like styles, javascript files or images
• conf – contains project configuration files:
  • application.yml contains standard web app settings like data source, mime types, and other Grails or Spring related settings
  • resources.groovy contains spring bean definitions
  • logback.groovy contains logging configuration
• controllers – responsible for handling requests and generating responses or delegating them to the views. By convention, when a file name ends with *Controller, the framework creates a default URL mapping for each action defined in the controller class
• domain – contains the business model of the Grails application. Each class living here will be mapped to database tables by GORM
• i18n – used for internationalization support
• init – an entry point of the application
• services – the business logic of the application will live here. By convention, Grails will create a Spring singleton bean for each service
• taglib – the place for custom tag libraries
• views – contains views and templates

Grails incorporates the powerful build system Gradle. The basic usage scenario is:

grails <<environment>>* <<command name>>

Grails searches in the following directories for Gant scripts to execute:

USER_HOME/.grails/scripts
PROJECT_HOME/src/main/scripts/
PROJECT_HOME/plugins/*/scripts
GRAILS_HOME/scripts

You can specify the environment that the command executes in with an optional environment parameter, either with one of the built-in environment names:

grails dev run-app
grails test run-app
grails prod run-app

The war command creates a Web Application Archive (WAR) file which can be deployed on any Java EE compliant application server.

grails [environment]* war [arguments]*

By default the war command creates a web application archive (WAR) file using the application name and version number. The war command is different from most commands since it runs in the production environment by default instead of development, but like any script the environment can be specified using the standard convention:

grails test war
grails dev war
grails prod war