concept object in category grails

appears as: objects, n object, object, object, objects
Grails in Action, Second Edition

This is an excerpt from Manning's book Grails in Action, Second Edition.

Ruby on Rails introduced the idea that XML configuration (or configuration of any sort) can be avoided if the framework makes opinionated choices for you about how things fit together. Grails embraces the same philosophy. Because your controller is called QuoteController, Grails will expose its actions over the URL /qotd/quote/your-action. Figure 1.4 gives a visual breakdown of how URLs translate to Grails objects.

Listing 3.7. Sharing constraints between objects

If your migrations use Grails domain class properties, you’re making a contract with the plugin that the properties you reference will be there for all time. (Because they must exist at the time the migration runs, they can never be renamed or removed in your application.) If you ever change any property’s references in the GORM migration and then attempt to create your database from scratch on a new machine, the migration will fail because the object no longer has those fields.

10.5.1. Making objects searchable

The first step in using the searchable plugin is determining the objects to index. In the case of Hubbub, users want to search on Post object content (to see posts matching a term) and also on the User object (does my friend “Joe Cool” have an account?).