List of usage examples for org.hibernate.engine.jdbc.connections.spi MultiTenantConnectionProvider interface-usage
From source file br.com.fabiose.book.utils.MultiTenantConnectionProviderImpl.java
/** * * @author fabioestrela */ public class MultiTenantConnectionProviderImpl implements MultiTenantConnectionProvider, ServiceRegistryAwareService {
From source file br.com.uktech.multitenantschema.multitenant.ConfigurableMultiTenantConnectionProvider.java
/** * * @author Carlos Alberto Cipriano Korovsky <carlos.korovsky at gmail.com> */ public class ConfigurableMultiTenantConnectionProvider implements MultiTenantConnectionProvider {
From source file com.billkoch.examples.hibernate.SchemaBasedTenantConnectionProvider.java
@Slf4j public class SchemaBasedTenantConnectionProvider implements MultiTenantConnectionProvider { private final DataSource dataSource; private final String schemaSelectionQuery;
From source file org.demoiselle.livraria.core.MultiTenantProvider.java
/**
* Implementation of @MultiTenantConnectionProvider in Hibernate.
*
* @author SERPRO
*
*/
From source file org.egov.infra.config.persistence.multitenancy.MultiTenantDatabaseConnectionProvider.java
@SuppressWarnings("all") public class MultiTenantDatabaseConnectionProvider extends TenantDatasourceProvider implements MultiTenantConnectionProvider { private static final long serialVersionUID = -4318080892788400229L;
From source file org.egov.infra.config.persistence.multitenancy.MultiTenantSchemaConnectionProvider.java
public class MultiTenantSchemaConnectionProvider implements MultiTenantConnectionProvider { private static final long serialVersionUID = -6022082859572861041L; private static final Logger LOG = LoggerFactory.getLogger(MultiTenantSchemaConnectionProvider.class); @Autowired private transient DataSource dataSource;
From source file org.opentides.persistence.hibernate.MultiTenantConnectionProviderImpl.java
/**
* For supporting multi-tenancy applications.
*
* Simple implementation using a single connection pool used to serve multiple
* schemas using "connection altering". This approach assumes one application server
* connects to only one database server and connection pool is shared across