I’m pleased to announce the availability of Spring Cloud Connectors 1.2.0.
Applications that use Spring Cloud Connectors, and libraries that extend the core Connectors libraries, should be re-compiled against version 1.2.0. There were no backward-incompatible API changes between version 1.1.1 and 1.2.0, but some internal implementation changes prevent 1.2.0 from being a drop-in replacement for 1.1.1 without re-compiling.
Here’s an overview of what’s new in 1.2.0:
The Cloud Foundry Connector and Spring Connector now support IBM DB2 and Microsoft SQL Server relational databases.
AmqpServiceInfono longer validates that the path element of a URI contains a value, which allows the default RabbitMQ vhost to be used.
- URL validation in
AmqpServiceInfowas relaxed such that QPID URL format is supported as well as RabbitMQ URL format.
AmqpServiceInfonow supports holding a list of URIs for providers that support multiple host connections.
- All relational database
ServiceInfoparsers now honor a
jdbcUrlfield in the
VCAP_SERVICES. If a
jdbcUrlis found, its value is provided by
RelationalServiceInfo.getJdbcUrlwithout modification. If a
jdbcUrlis not found, then a JDBC URL will be constructed by
- The AMQP
ServiceInfoparser now supports multiple URIs as provided by Pivotal’s RabbitMQ for Pivotal Cloud Foundry version 1.4.
- The AMQP
ServiceInfoparser now parses the management API and makes it available to clients.
amqpswas added as a valid scheme when detecting an AMQP service based on a
urlfield in the
- There was an issue with nested
@Configurationclasses that extend
ClassNotFoundexceptions when spring-data-jpa, spring-data-mongodb, spring-data-redis, or spring-amqp are not present on the runtime classpath. This issue has been resolved, so only the dependencies actually needed by the application are required at runtime.
- The HikariCP connection pooling library is now supported when creating a
DataSource, along with Tomcat and Apache Commons pooling libraries.
- The Tomcat connection pooling support will now work with Tomcat 7 or Tomcat 8 DBCP libraries.
RabbitConnectionFactoryConfigwill now accept a map of key/value pairs to allow setting arbitrary properties of the created
ConnectionFactory. This can be used by Java configuration or XML configuration.
RedisConnectionFactoryConfigwill now accept a map of key/value pairs to allow setting arbitrary properties of the created
RedisConnectionFactory. This can be used by Java configuration or XML configuration.
MongoDbFactoryCreatornow passes the authSource from the URI to the
MongoDbFactoryCreatornow accepts a URL that contains a list of replica sets.