Class and Description |
---|
io.vertx.core.Starter
Use
Launcher instead |
Field and Description |
---|
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_HOST
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_HOST instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_PING_INTERVAL
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_PING_INTERVAL instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_PING_REPLY_INTERVAL
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_PING_REPLY_INTERVAL instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_PORT
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_PORT instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_PUBLIC_HOST
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_PUBLIC_HOST instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTER_PUBLIC_PORT
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTER_PUBLIC_PORT instead |
io.vertx.core.VertxOptions.DEFAULT_CLUSTERED
as of 3.7, use
EventBusOptions.DEFAULT_CLUSTERED instead |
Method and Description |
---|
io.vertx.core.net.SSLEngineOptions.clone()
use
SSLEngineOptions.copy() instead |
io.vertx.core.net.TrustOptions.clone()
use
TrustOptions.copy() instead |
io.vertx.core.net.KeyCertOptions.clone()
use
KeyCertOptions.copy() instead |
io.vertx.core.Future.completer()
use this object instead since it extends
Handler<AsyncResult<T>> |
io.vertx.core.http.HttpClient.delete(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.delete(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.delete(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.delete(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.deleteAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClientRequest.endHandler(Handler<Void>)
this method will be removed in Vert.x 4
|
io.vertx.core.http.HttpClientRequest.fetch(long)
this method will be removed in Vert.x 4
|
io.vertx.core.http.HttpClient.get(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.get(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.get(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.get(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.getAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.VertxOptions.getClusterHost()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getHost() instead |
io.vertx.core.VertxOptions.getClusterPingInterval()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getClusterPingInterval() instead |
io.vertx.core.VertxOptions.getClusterPingReplyInterval()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getClusterPingReplyInterval() instead |
io.vertx.core.VertxOptions.getClusterPort()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getPort() instead |
io.vertx.core.VertxOptions.getClusterPublicHost()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getClusterPublicHost() instead |
io.vertx.core.VertxOptions.getClusterPublicPort()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.getClusterPublicPort() instead |
io.vertx.core.http.HttpClient.getNow(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.getNow(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.getNow(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.getNow(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.cli.CommandLine.getRawValues(Option) |
io.vertx.core.http.HttpClientRequest.handler(Handler<HttpClientResponse>)
this method will break in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> |
io.vertx.core.http.HttpClient.head(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.head(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.head(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.head(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.headAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.headNow(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.headNow(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.headNow(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.headNow(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.net.NetServerOptions.isClientAuthRequired()
use
getClientAuth() == ClientAuth.REQUIRED instead |
io.vertx.core.VertxOptions.isClustered()
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.isClustered() instead |
io.vertx.core.spi.metrics.Metrics.isEnabled()
the SPI metrics should instead return a
null object to signal that metrics is not provided |
io.vertx.core.VertxOptions.isFileResolverCachingEnabled()
use
getFileSystemOptions().getFileCachingEnabled() instead |
io.vertx.core.net.TCPSSLOptions.isUsePooledBuffers()
this has no effect, just don't use it
|
io.vertx.core.http.HttpClient.options(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.options(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.options(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.options(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.optionsAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.optionsNow(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.optionsNow(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.optionsNow(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.optionsNow(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClientRequest.pause()
this method will be removed in Vert.x 4
|
io.vertx.core.http.HttpClient.post(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.post(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.post(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.post(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.postAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.put(int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.put(RequestOptions, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.put(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.put(String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.putAbs(String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.request(HttpMethod, int, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.request(HttpMethod, RequestOptions, Handler<HttpClientResponse>)
this method will break in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> |
io.vertx.core.http.HttpClient.request(HttpMethod, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.request(HttpMethod, String, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClient.requestAbs(HttpMethod, String, Handler<HttpClientResponse>)
this method signature will change in Vert.x 4, the handler will use an
Handler<AsyncResult<HttpClientResponse>> ,
you can use instead the WebClient |
io.vertx.core.http.HttpClientRequest.resume()
this method will be removed in Vert.x 4
|
io.vertx.core.net.NetServerOptions.setClientAuthRequired(boolean)
use
setClientAuth(ClientAuth.REQUIRED) or setClientAuth(ClientAuth.NONE) instead |
io.vertx.core.http.HttpServerOptions.setClientAuthRequired(boolean) |
io.vertx.core.VertxOptions.setClustered(boolean)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setClustered(boolean) instead |
io.vertx.core.VertxOptions.setClusterHost(String)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setHost(String) instead |
io.vertx.core.VertxOptions.setClusterPingInterval(long)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setClusterPingInterval(long) instead |
io.vertx.core.VertxOptions.setClusterPingReplyInterval(long)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setClusterPingReplyInterval(long) instead |
io.vertx.core.VertxOptions.setClusterPort(int)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setPort(int) instead |
io.vertx.core.VertxOptions.setClusterPublicHost(String)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setClusterPublicHost(String) instead |
io.vertx.core.VertxOptions.setClusterPublicPort(int)
as of 3.7, use
VertxOptions.getEventBusOptions() and then EventBusOptions.setClusterPublicPort(int) instead |
io.vertx.core.VertxOptions.setFileResolverCachingEnabled(boolean) |
io.vertx.core.DeploymentOptions.setMultiThreaded(boolean)
as of 3.6.0
|
io.vertx.core.net.TCPSSLOptions.setUsePooledBuffers(boolean)
this has no effect, just don't use it
|
Copyright © 2019 Eclipse. All rights reserved.