Navigation :
test ../ test dev.html
Developer Guide
test ../ test dev/dev-release.html
-
Release and migration notes
test ../ test dev/getting-started.html
-
Getting started
test ../ test dev/dev-ui-config.html
-
Configuring the UI
test ../ test dev/dev-extensions.html
-
Extending the Module
test ../ test dev/integration.html
-
How to Connect Limits to an Atoti Server
test ../ test dev/alert-tasks.html
-
Evaluating Limits
test ../ test dev/scopes.html
-
Limit Scopes
test ../ test dev/limit-workflow.html
-
Limit Workflow
test ../ test dev/date-roll.html
- Date Roll
test ../ test dev/restful-endpoint.html
- RESTful endpoints
test ../ test dev/security.html
- Required Roles
test ../ test user-ref.html
User & Reference Guide
test ../ test user-ref/limits-overview.html
-
Atoti Limits Overview
test ../ test user-ref/whats-new.html
- What's New
test ../ test user-ref/using-limits.html
-
Manage limits
test ../ test user-ref/manage-incidents.html
-
Manage incidents
test ../ test user-ref/input-files.html
-
Input file formats
test ../ test user-ref/configuration.html
-
Configuration files
test ../ test user-ref/cube.html
-
Cube reference
test ../ test user-ref/datastore.html
-
Datastores
Extending the Module
This section explains how to extend Atoti Limits services by adding customizations.
Overview
In general, services in Atoti Limits can be extended by:
Defining a Spring Bean that implements the interface represented by the service
Marking the bean as Primary
Importing the bean into your project
Importing Spring Beans into the Project
Customizations that override an existing default implementation will usually require importing your custom Spring Bean. The LimitsAppConfig
class is the main entry-point in Atoti Limits for imports, so if you need to import your MyCustomBean
class, you should do so here. For example:
@Configuration
@Import ({
// Default imports start ...
// ...
// ... default imports end
// Custom imports
MyCustomBean. class
})
public class LimitsAppConfig {
// other code...
}