Class DatasourceConnectionProviderImpl

    • Constructor Detail

      • DatasourceConnectionProviderImpl

        public DatasourceConnectionProviderImpl()
    • Method Detail

      • getDataSource

        public DataSource getDataSource()
      • setDataSource

        public void setDataSource​(DataSource dataSource)
      • setJndiService

        public void setJndiService​(JndiService jndiService)
      • isUnwrappableAs

        public boolean isUnwrappableAs​(Class<?> unwrapType)
        Description copied from interface: Wrapped
        Can this wrapped service be unwrapped as the indicated type?
        Specified by:
        isUnwrappableAs in interface Wrapped
        unwrapType - The type to check.
      • unwrap

        public <T> T unwrap​(Class<T> unwrapType)
        Description copied from interface: Wrapped
        Unproxy the service proxy
        Specified by:
        unwrap in interface Wrapped
        unwrapType - The java type as which to unwrap this instance.
        The unwrapped reference
      • configure

        public void configure​(Map<String,​Object> configValues)
        Description copied from interface: Configurable
        Configure the service.
        Specified by:
        configure in interface Configurable
        configValues - The configuration properties.
      • stop

        public void stop()
        Description copied from interface: Stoppable
        Stop phase notification
        Specified by:
        stop in interface Stoppable
      • supportsAggressiveRelease

        public boolean supportsAggressiveRelease()
        Description copied from interface: ConnectionProvider
        Does this connection provider support aggressive release of JDBC connections and later re-acquisition of those connections if needed?

        This is used in conjunction with ConnectionReleaseMode.AFTER_STATEMENT to aggressively release JDBC connections. However, the configured ConnectionProvider must support re-acquisition of the same underlying connection for that semantic to work.

        Typically, this is only true in managed environments where a container tracks connections by transaction or thread. Note that JTA semantic depends on the fact that the underlying connection provider does support aggressive release.

        Specified by:
        supportsAggressiveRelease in interface ConnectionProvider
        true if aggressive releasing is supported; false otherwise.