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

Hadrian Zbarcea commented on CAMEL-527:
---------------------------------------

That would work.  I took care of that, but there are a few others to sort out.  
I think we can remove language -> component, model -> component and model -> 
language.  I am not sure what we can do with camel <-> model because of 
RouteType.

> Break dependency cycle between camel and camel.impl
> ---------------------------------------------------
>
>                 Key: CAMEL-527
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-527
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Christian Schneider
>            Assignee: Claus Ibsen
>             Fix For: 1.4.0
>
>         Attachments: 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 impl. 
> 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.

Reply via email to