Engineering
Releases
News and Events

Spring Cloud Connectors 1.2.0 released

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:

Additional Databases Supported

The Cloud Foundry Connector and Spring Connector now support IBM DB2 and Microsoft SQL Server relational databases.

Spring Cloud Connectors Core

AMQP

  • AmqpServiceInfo no longer validates that the path element of a URI contains a value, which allows the default RabbitMQ vhost to be used.
  • URL validation in AmqpServiceInfo was relaxed such that QPID URL format is supported as well as RabbitMQ URL format.
  • AmqpServiceInfo now supports holding a list of URIs for providers that support multiple host connections.

Cloud Foundry Connector

Relational Databases

  • All relational database ServiceInfo parsers now honor a jdbcUrl field in the credentials contained in VCAP_SERVICES. If a jdbcUrl is found, its value is provided by RelationalServiceInfo.getJdbcUrl without modification. If a jdbcUrl is not found, then a JDBC URL will be constructed by RelationalServiceInfo as before.

AMQP

  • The AMQP ServiceInfo parser now supports multiple URIs as provided by Pivotal’s RabbitMQ for Pivotal Cloud Foundry version 1.4.
  • The AMQP ServiceInfo parser now parses the management API and makes it available to clients.
  • amqps was added as a valid scheme when detecting an AMQP service based on a url field in the credentials contained in VCAP_SERVICES.

Spring Connector

Java Configuration

  • There was an issue with nested @Configuration classes that extend AbstractCloudConfig triggering ClassNotFound exceptions 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.

Relational Databases

  • 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.

RabbitMQ

  • RabbitConnectionFactoryConfig will 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.

Redis

  • RedisConnectionFactoryConfig will 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.

MongoDB

  • MongoDbFactoryCreator now passes the authSource from the URI to the MongoDbFactory.
  • MongoDbFactoryCreator now accepts a URL that contains a list of replica sets.
comments powered by Disqus