DiVine
  • Introduction
  • Getting Started
    • Installation
    • Quickstart
  • Advanced usage
    • Service scopes
    • Service factories
    • Service implementations
      • Implementation permissions
    • Custom annotations
    • Circular dependencies
      • Referenced dependency access
      • Lazy dependency access
    • Service lifecycles
      • Post construction
      • Lazy post construction
      • Post termination
    • Multiple constructors
    • Dependency hooks
    • Runtime exceptions
  • Best practices
    • Using lombok
    • Keep it simple
    • Structure your code
Powered by GitBook
On this page
  1. Advanced usage
  2. Service implementations

Implementation permissions

PreviousService implementationsNextCustom annotations

Last updated 4 months ago

You can create a rule for the service interface, that specifies, which classes may implement the interface.

@Service(permits = { MongoUserService.class, MySQLUserService.class })
interface UserService {
}

@Service
class MongoUserService implements UserService {
}

@Service
class MySQLUserService implements UserService {
}

@Service
class PostgresUserService implements UserService {
}

void initUserService() {
    Container.implement(UserService.class, MongoUserService.class);
    Container.implement(UserService.class, MySQLUSerService.class);
    // both should work fine
    
    Container.implement(UserService.class, PostgresUserService.class); 
    // will throw an `InvalidServiceAccessException`
}