camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-4464) Resolve cycle bettween processor package and its subpackages
Date Mon, 19 Sep 2011 08:34:09 GMT

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

Christian Schneider updated CAMEL-4464:
---------------------------------------

    Attachment: CAMEL-4464_after.png
                CAMEL-4464_before.png

> Resolve cycle bettween processor package and its subpackages
> ------------------------------------------------------------
>
>                 Key: CAMEL-4464
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4464
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.8.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 2.9.0
>
>         Attachments: CAMEL-4464_after.png, CAMEL-4464_before.png
>
>
> The processor package and its subpackages interceptor and aggregator form a dependency
cycle.
> The first cycle is between processor and processor.interceptor. The package interceptor
needs several processor classes so this direction can not be avoided easily. Int the other
direction DefaultChannel depends on interceptor clases. Interestingly DefaultChannel is not
used from other classes in processor. So I propose to jsut move DefaultChannel to interceptor
to keep interceptor related stuff together.
> The second cycle is between processor and processor.aggregate. The AggregateProcessor
uses the SendProcessor. Here I propose to just use a producerTemplate to end the failed exchange.
ProducerTemplate is a API element and can be fetched from the camelContext so this solves
the cycle. I hope that using the ProducerTemplate does not create other issues. The tests
seem to work.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message