Release Notes for Eclipse Vert.x 3.9

The following section explains the changes in EventBus JavaScript client.

The value accessor methods in Row and Tuple throw exceptions instead of returning null for invalid values.

When several instances of the same verticle use the wildcard port (0), the first instance binds to a random port and all the other instances also bind to the same random port.

In releases prior to Eclipse Vert.x 3.9.2, all the instances of the same verticle that used the wildcard port (0) were bound to different random ports.

The prepared statements that are created using the SqlConnection.Prepare method are no longer cached internally. If you want to cache the prepared statements, you must set up the caching.

The PgConnection.Prepare method creates a named prepared statement. In the previous releases, the method created unnamed prepared statements.

The Red Hat build of Eclipse Vert.x for s390x and ppc64le platforms is supported only in OpenShift environments provisioned on IBM Z and IBM Power Systems infrastructure. Running an Eclipse Vert.x application on a stand-alone installation of RHEL on IBM Z and IBM Power Systems is not supported.

Eclipse OpenJ9 Java images for IBM Z, IBM Power Systems and new images for products supported on IBM Z and IBM Power Systems are available in the Red Hat Ecosystem Catalog.

To deploy the example applications on OpenShift environments provisioned on IBM Z and IBM Power Systems infrastructure, specify the relevant IBM Z or IBM Power Systems image name in the pom.xml file and commands.

Some of the example applications also require other products, such as Red Hat Data Grid to demonstrate the workflows. In this case, you must also change the image names of these products to their relevant IBM Z or IBM Power Systems image names in the YAML file of the example applications.

The new class Query is a fluent API. It enables you to create and configure queries before their execution. All the query collectors are available in the Query interface.

The new class PreparedStatement enables you to create and execute prepared statements. The prepared statements can execute multiple interactions such as cursor or stream operations.

The existing class PreparedQuery extends the new class Query. The class can now be used outside the context of the connection.

For example, use the following sample codes to create queries:

The MqttClientOptions.getKeepAliveTimeSeconds() and MqttClientOptions.setKeepAliveTimeSeconds() methods have been deprecated. Use the MqttClientOptions.getKeepAliveInterval() and MqttClientOptions.setKeepAliveInterval() methods instead to get and set the keep alive interval in seconds.

The HttpServerRequest.netSocket() method has been deprecated. Use the new method HttpServerRequest.toNetSocket() instead to establish a TCP tunnel with the client.

The following example shows you how the deprecated method HttpServerRequest.netSocket() was used.

NetSocket sock = request.netSocket();

NetSocket sock = request.netSocket();

The following example shows you how to use the new method HttpServerRequest.toNetSocket().

request.response().toNetSocket(ar -> {
  if (ar.succeeded()) {
    NetSocket sock = ar.result();
  }

request.response().toNetSocket(ar -> {
  if (ar.succeeded()) {
    NetSocket sock = ar.result();
  }

The HttpServerRequest.upgrade() method has been deprecated. Use the new method HttpServerResponse.toWebSocket() instead to upgrade the connection of the current request to a WebSocket.

The following example shows you how the deprecated method HttpServerRequest.upgrade() was used.

ServerWebSocket ws = request.upgrade();

ServerWebSocket ws = request.upgrade();

The following example shows you how to use the new method HttpServerResponse.toWebSocket().

request.response().toWebSocket(ar -> {
  if (ar.succeeded()) {
    ServerWebSocket ws = ar.result();
  }
});

request.response().toWebSocket(ar -> {
  if (ar.succeeded()) {
    ServerWebSocket ws = ar.result();
  }
});

The sockjs.BridgeOptions class has been deprecated. Use the new sockjs.SockJSBridgeOptions class instead. The sockjs.SockJSBridgeOptions class contains all the options that are required to configure the event bus bridge.

There is no change in the behavior of the new class, except that the name of the data object class has changed. When new bridges were added, there were a lot of duplicate configurations. The new class contains all the possible common configurations, and removes duplicate configurations.

The verticle methods start(Future<Void>) and stop(Future<Void>) have been deprecated. Use the methods start(Promise<Void>) and stop(Promise<Void>) to work with promise.

The extension mechanism for DNS is disabled by default in Eclipse Vert.x. To enable EDNS use the method AddressResolverOptions.setOptResourceEnabled(). Specify the input parameter optResourceEnabled as true.

The following new handler methods are available:

The AdminUtils class is no longer available. Use the new KafkaAdminClient class instead to perform administrative operations on a Kafka cluster.

The updates in the HTTP methods for WebSocket are:

The following authentication and authorization classes and methods are deprecated and will be replaced in a future release.

Use the following new methods to create clients that do not have shared data sources with other clients. These methods maintain their own data sources.