You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2025/05/30 12:04:00 UTC

[jira] [Comment Edited] (CAMEL-20015) camel-core: cleanup cyclic dependencies in the AbstractExchange

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

Claus Ibsen edited comment on CAMEL-20015 at 5/30/25 12:03 PM:
---------------------------------------------------------------

Move more stuff over to the extension

exchange properties and variables are still stored on abstract exchange, as they are user data and thus belong better there such as the message itself etc.


was (Author: davsclaus):
Move more stuff over to the extension

exchange properties and variables are still stored on abstract exchange. 

> camel-core: cleanup cyclic dependencies in the AbstractExchange
> ---------------------------------------------------------------
>
>                 Key: CAMEL-20015
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20015
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Otavio Rodolfo Piske
>            Assignee: Otavio Rodolfo Piske
>            Priority: Minor
>             Fix For: 4.x
>
>
> As part of CAMEL-15105 we decoupled the ExtendedExchange from the AbstractExchange. This helped us reduce the incidence of type polution problems, cleanup and simplify the code. 
> However, there's still many cases of cyclic dependencies between these two types. We should move the handling of the internal APIs fully to the extension class.  



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