-
Deprecated Interfaces
-
Deprecated ClassesClassDescription
-
Deprecated MethodsMethodDescriptionremoved from public API in Vert.x 5removed from public API in Vert.x 5instead use
Buffer.toJsonValue()instead useContext.executeBlocking(Callable)instead useContext.executeBlocking(Callable, boolean)instead useContext.executeBlocking(Callable)instead useContext.executeBlocking(Callable, boolean)removed in Vert.x 5no replacement for back-pressure, instead ignore the packet or buffer it somewhereno replacement for back-pressure, instead ignore the packet or buffer it somewhereno replacement for back-pressure, instead ignore the packet or buffer it somewhereinstead useHttpClientBuilder#withConnectHandler(Handler)instead useHttpClientBuilder.withRedirectHandler(Function)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(WebSocketConnectOptions, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useWebSocketClient#connect(int, String, String, Handler)instead useHttpClientRequest.authority(HostAndPort)instead useHttpClientRequest.authority(HostAndPort)instead useHttpClientRequest.idleTimeout(long)instead use#shutdown(long, TimeUnit, Handler)instead use#shutdown(long, TimeUnit, Handler)instead use#shutdown(long, TimeUnit, Handler)instead use#requestHandler(Handler)instead use#webSocketHandler(Handler)the implementation made a wrong assumption that cookies could be identified only by their name. The RFC states that the tuple of<name, domain, path>is the unique identifier. When more than one cookie has the same name, the map will hold that lost one to be parsed and any previously parsed value will be silently overwritten.instead useHttpServerRequest.authority()instead useHttpConnection.close()orHttpServerResponse.reset(long), this method is removed in Vert.x 5instead use#push(HttpMethod, HostAndPort, String, Handler)instead use#push(HttpMethod, HostAndPort, String, Handler)instead use#push(HttpMethod, HostAndPort, String, Handler)instead useServerWebSocketHandshake.accept()useServerWebSocket.authority()insteadinstead useServerWebSocketHandshake.reject()instead useServerWebSocketHandshake.reject(int)instead useServerWebSocketHandshakeinstead useServerWebSocketHandshakeinstead useServerWebSocketHandshakeinstead use#connectHandler(Handler)instead useVertx.executeBlocking(Callable)use insteadVertx.executeBlocking(Callable, boolean)instead useVertx.executeBlocking(Callable)use insteadVertx.executeBlocking(Callable, boolean)removed from public API in Vert.x 5useVertx.setPeriodic(long, java.util.function.Consumer<java.lang.Long>)instead. RxJava like integrations should use the Vert.x scheduler integration.useVertx.setPeriodic(long, java.util.function.Consumer<java.lang.Long>)instead. RxJava like integrations should use the Vert.x scheduler integration.useVertx.setTimer(long, java.util.function.Consumer<java.lang.Long>)instead. RxJava like integrations should use the Vert.x scheduler integration.instead useWorkerExecutor.executeBlocking(Callable)instead useWorkerExecutor.executeBlocking(Callable)For type safety this method should be avoided and#authenticate(Credentials, Handler)should be used instead.For type safety this method should be avoided and#authenticate(Credentials, Handler)should be used instead.For type safety this method should be avoided and#authenticate(Credentials, Handler)should be used instead.This factory is only for backwards compatibilityio.vertx.mutiny.ext.auth.jdbc.JDBCAuthorization.create(String, JDBCClient, JDBCAuthorizationOptions) Please useMongoUserUtilinstead. Insert a new user into mongo in the convenient wayPlease useMongoUserUtilinstead. Insert a new user into mongo in the convenient wayPlease useMongoUserUtilinstead. Insert a new user into mongo in the convenient wayFor type safety this method should be avoided andOAuth2Auth.authorizeURL(OAuth2AuthorizationURL)should be used instead.This method will be removed. UseAuthorizations#clear()Use typed alternative#isAuthorized(Authorization, Handler)Use typed alternative#isAuthorized(Authorization, Handler)Use typed alternative#isAuthorized(Authorization, Handler)UseConsulClient.deleteAclToken(String)insteadUseConsulClient.deleteAclToken(String)insteadUseConsulClient.deleteAclToken(String)insteadUseConsulClient.readAclToken(String)insteadUseConsulClient.readAclToken(String)insteadUseConsulClient.readAclToken(String)insteadUseConsulClient.getAclTokens()insteadUseConsulClient.getAclTokens()insteadUseConsulClient.getAclTokens()insteadSeeTermServer.authenticationProvider(AuthenticationProvider)Set an auth provider to use, any provider configured in options will override this provider. This should be used when a custom auth provider should be used.instead useSQLConnection.setOptions(SQLOptions)withSQLOptions.setQueryTimeout(int)Router Factory won't manage the validation errors anymore. You must useRouter.errorHandler(int, Handler)with 400 errorYou must useRouter.errorHandler(int, Handler)with 501 errorio.vertx.mutiny.ext.web.api.contract.openapi3.OpenAPI3RouterFactory.setOptions(RouterFactoryOptions) Router Factory won't manage the validation errors anymore. You must useRouter.errorHandler(int, Handler)with 400 errorRouter Factory won't manage the validation errors anymore. You must useRouter.errorHandler(int, Handler)with 400 errorYou must useRouter.errorHandler(int, Handler)with 501 errorRouter Factory won't manage the validation errors anymore. You must useRouter.errorHandler(int, Handler)with 400 errorinstead useHttpResponseExpectationalong withFuture.expecting(Expectation)instead useHttpResponseExpectationalong withFuture.expecting(Expectation)useChainAuthHandler.any()instead.patterns should use the relative origin method. Create a CORS handler using a regular expression to match origins. An origin follows rfc6454#section-7 and is expected to have the format:<scheme> "://" <hostname> [ ":" <port> ]io.vertx.mutiny.ext.web.handler.graphql.ApolloWSHandler.connectionHandler(Consumer<ServerWebSocket>) as of 4.2, use#beforeExecute(Handler)insteadas of 4.2, use#beforeExecute(Handler)insteadas of 4.2, use#beforeExecute(Handler)insteadas of 4.5.1, useGraphiQLHandler.create(Vertx), withGraphiQLHandler.router()as of 4.5.1, useGraphiQLHandler.create(Vertx, GraphiQLHandlerOptions), withGraphiQLHandler.router()as of 4.5.1, useGraphiQLHandler.builder(Vertx)insteadas of 4.5.1, useGraphQLHandler.builder(GraphQL)insteadas of 4.2, use#beforeExecute(Handler)insteadinvokeGraphQLContext.get(Object)withRoutingContextclass object instead.as of 4.2, use#beforeExecute(Handler)insteadas of 4.2, use#beforeExecute(Handler)insteadas of 4.5.1, useGraphQLWSHandler.builder(GraphQL)insteadas of 4.5.1, useGraphQLWSHandler.builder(GraphQL)insteadas of 4.5.1, useGraphQLWSHandler.builder(GraphQL)insteadas of 4.5.1, useGraphQLWSHandler.builder(GraphQL)insteadSuperseded byLoggerHandler.customFormatter(LoggerFormatter)mount the router as a sub-router instead. This method will not properly handle errors.Use#rootHandler(Handler)instead. The order matters, so adding the body handler should happen after anyPLATFORMorSECURITY_POLICYhandler(s).This method exposes the internal of the OpenAPI handler, it will be removed in the future. Users should configure the json schema module from the options.This method exposes the internal of the OpenAPI handler, it will be removed in the future. Users should configure the json schema module from the options.This method duplicates the sub router functionality fromRoute.subRouter(Router). Mount a sub router on this routerUseHttpServerResponse#addCookie(Cookie)Add a cookie. This will be sent back to the client in the response.instead useUserContext.logout()UseHttpServerRequest#cookieCount()UseHttpServerRequest#cookieMap()UseRoutingContext.body()instead.UseRoutingContext.body()instead.UseRoutingContext.body()instead. Gets the current body buffer as aJsonObject. If a positive limit is provided the parsing will only happen if the buffer length is smaller or equal to the limit. Otherwise anIllegalStateExceptionis thrown. When the application is only handling uploads in JSON format, it is recommended to set a limit onBodyHandler.setBodyLimit(long)as this will avoid the upload to be parsed and loaded into the application memory.UseRoutingContext.body()instead.UseRoutingContext.body()instead. Gets the current body buffer as aJsonArray. If a positive limit is provided the parsing will only happen if the buffer length is smaller or equal to the limit. Otherwise anIllegalStateExceptionis thrown. When the application is only handling uploads in JSON format, it is recommended to set a limit onBodyHandler.setBodyLimit(long)as this will avoid the upload to be parsed and loaded into the application memory.UseRoutingContext.body()instead.UseRoutingContext.body()instead. Get the entire HTTP request body as a string, assuming the specified encoding. The context must have first been routed to aBodyHandlerfor this to be populated.UseHttpServerRequest#getCookie(String)Get the cookie with the specified name.UseHttpServerResponse#removeCookie(String)Expire a cookie, notifying a User Agent to remove it from its cookie jar.UseHttpServerResponse#removeCookie(String, boolean)Remove a cookie from the cookie set. If invalidate is true then it will expire a cookie, notifying a User Agent to remove it from its cookie jar.This method is internal. Users that really need to use it should refer toRoutingContextInternal.setBody(Buffer)Set the body. Used by theBodyHandler. You will not normally call this method.This method is internal. Users that really need to use it should refer toio.vertx.ext.web.impl.RoutingContextInternal#setSession(Session)Set the session. Used by theSessionHandler. You will not normally call this method.this method should not be called, application authentication should rely onAuthenticationHandlerimplementations.seeTemplateEngine.unwrap()Set the mode for the engineThis method duplicates the behavior ofValidationHandlerBuilder#create(SchemaParser).io.vertx.mutiny.json.schema.SchemaRouter.resolveCachedSchema(JsonPointer, JsonPointer, SchemaParser) io.vertx.mutiny.json.schema.SchemaRouter.resolveRefAndForget(JsonPointer, JsonPointer, SchemaParser) REDIS does not supportnullas a parameter, only as response. This was a deviation from the official protocol which should be avoided. Other clients explicitly do not allow this. Adds anullencoded string. Redis does not allow storing thenullvalue by itself. This method will encode any null value as the four character long string"null". As a recommendation, this method should not be used directly unless this is the intented behavior. It is present to handle special cases such as encoding ofJsonObjectandJsonArraywhich may contain null values.instead useClientBuilder#withConnectHandler(Handler)instead useClientBuilder.connectingTo(Supplier)
CircuitBreaker.retryPolicy(RetryPolicy)instead