You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2026/04/30 12:32:00 UTC

[jira] [Commented] (CAMEL-20009) Migrate internal code from deprecated getOut to getMessage

    [ https://issues.apache.org/jira/browse/CAMEL-20009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077326#comment-18077326 ] 

Guillaume Nodet commented on CAMEL-20009:
-----------------------------------------

This issue is being addressed in PR https://github.com/apache/camel/pull/22358, targeting Camel 5.x.

The PR migrates all deprecated Exchange getOut/hasOut/setOut calls to the modern getMessage API, introducing ExchangeHelper bridge methods (hasResponse, getResponse, setResponse, createResponse, createResponseFromInput).

_Claude Code on behalf of Guillaume Nodet_

> Migrate internal code from deprecated getOut to getMessage
> ----------------------------------------------------------
>
>                 Key: CAMEL-20009
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20009
>             Project: Camel
>          Issue Type: Task
>            Reporter: Aurélien Pupier
>            Priority: Major
>             Fix For: 5.x
>
>
> several components are still using getOut which was deprecated in Camel 3.
> The documentation is still using getOut https://camel.apache.org/manual/faq/using-getin-or-getout-methods-on-exchange.html
> tests should have been migrated [CAMEL-14020] already



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