camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <>
Subject [jira] Commented: (CAMEL-527) Break dependency cycle between camel and camel.impl
Date Wed, 04 Jun 2008 13:17:00 GMT


Hadrian Zbarcea commented on CAMEL-527:


I think this kind of changes have a big impact on other projects using  
camel, such as activemq and servicemix.  Not only code changes are  
required in these projects, but their ability to work with different  
versions of camel.  This has a cascading effect on users of such  
projects who may have to consider updating to camel 1.4 too.

I would suggest asking their opinion in the future before making such  

My $0.02,

> Break dependency cycle between camel and camel.impl
> ---------------------------------------------------
>                 Key: CAMEL-527
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Christian Schneider
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.4.0
>         Attachments: producertemplate.patch, servicehelper.patch
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
> Currently there is a dependency cycle between camel and camel.impl. While I think there
is no problem when impl uses camel the other direction should not occur. Luckily there ist
only one case where this happens. The class CamelTemplate from camel uses ServiceSupport from
> As a solution I would suggest to move ServiceSupport and Service to util. ServiceHelper
is already in util and Service as well as ServiceSupport do not need any other classes. This
would help to break the dependency cycle and at the same time move some classes out of the
already quite big camel package.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message