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

["Otavio Rodolfo Piske (Jira)" <ji...@apache.org>]

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

Otavio Rodolfo Piske updated CAMEL-20015:
-----------------------------------------
    Description: 
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.  

  was:
As part of CAMEL-15105 we decoupled the ExtendedCamelContext from the AbstractCamelContext. 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.  


> 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: Major
>
> 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)