A running instance of Play is built around the
Application class, the starting point for most of the application state for Play. The Application is loaded through an
ApplicationLoader and is configured with a disposable classloader so that changing a setting in development mode will reload the Application. Most of the
Application settings are configurable, but more complex behavior can be hooked into Play by binding the various handlers to a specific instance through dependency injection.
Note: Application configuration has changed in Play 2.5.x so that dependency injection is the primary method of configuration.
Configuring the application through
GlobalSettingsclass is still available through Global Settings, but is deprecated and may be removed in future versions. Please see the Removing `GlobalSettings` page for how to migrate away from GlobalSettings.
Next: Essential Actions
Found an error in this documentation? The source code for this page can be found here. After reading the documentation guidelines, please feel free to contribute a pull request. Have questions or advice to share? Go to our community forums to start a conversation with the community.