3.5.0 Breaking Changes
Julien Viet edited this page Oct 10, 2017
·
13 revisions
-
JWTAuth
create method now takesJWTAuthOptions
instead ofJsonObject
for configuration. This brings more type safety to the config and less undocumented features of the provider. https://github.com/vert-x3/vertx-auth/pull/124 -
Oauth2Auth
the methodgetToken
is now deprecated and replaced by the commonauthenticate
https://github.com/vert-x3/vertx-auth/pull/156 -
OAuth2Auth
the methodapi
is removed as it was supposed to be an internal helper to get a Token and is not suitable for usage outside that. A new Apifetch
is added to theAccessToken
for general use.
- Hazelcast has been upgraded to 3.8.2. All nodes in the cluster should use Hazelcast 3.7+. See the Hazelcast Compatibility Matrix
- The
publishCompleteHandler
in theMqttEndpoint
interface is now renamed inpublishCompletionHandler
to be aligned with handler naming convention in all others Vert.x components.
-
io.vertx.ext.web.handler.sockjs.BridgeEventType
enum has been removed and you should use:io.vertx.ext.bridge.BridgeEventType
enum instead. -
SessionStore
put, clear, delete take inAsyncResult<Void>
instead ofAsyncResult<Boolean>
as the value was always true and did not reflect if the operation succeeded.
- In case the key is not found, the methods
ConsulClient#getValue()
andConsulClient#getValueWithOptions()
provides an emptyKeyValue
object instead of an failedAsyncResult
- In case the key prefix is not found, the methods
ConsulClient#getValues()
andConsulClient#getValuesWithOptions()
provides an emptyKeyValueList
object instead of an failedAsyncResult
- Watchers must handle
WatchResult
object instead ofAsyncResult
- In clustered mode the service discovery default backend has been updated to use another strategy. All member needs to be updates to read / write in this new backend.
- All predicate methods end with question mark again (lost in 3.4). It is idiomatic in Ruby.
- The automatic migration path for Verticles written against the previous API has been removed - Vert.x 3.5.0 assumes that applications have been migrated to the new API.