You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2023/10/18 13:05:00 UTC

[jira] [Assigned] (CAMEL-20011) camel-vertx: Avoid usage of deprecated Vertx.executeBlocking(Handler>)

     [ https://issues.apache.org/jira/browse/CAMEL-20011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Netherton reassigned CAMEL-20011:
---------------------------------------

    Assignee: James Netherton

> camel-vertx: Avoid usage of deprecated Vertx.executeBlocking(Handler<Promise<T>>)
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-20011
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20011
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>
> In Vert.x 4.5.5, the method signature that we use in various components for Vertx.executeBlocking became deprecated. E.g
> executeBlocking(Handler<Promise<T>> blockingCodeHandler)
> Is deprecated in favor of:
> executeBlocking(Callable<T> blockingCodeHandler)
> It'd be good to migrate the following components to use the preferred signature if possible.
> * camel-knative-http (See KnativeHttpConsumer & KnativeHttpTest)
> * camel-platform-http-vertx (See VertxPlatformHttpConsumer)
> * camel-reactive-executor-vertx (See VertXReactiveExecutor)
> * camel-threadpoolfactory-vertx (See VertXThreadPoolFactory)
> * camel-vertx-websocket (See VertxWebsocketConsumer & VertxWebsocketClientConsumer)
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)