[
https://issues.apache.org/activemq/browse/CAMEL-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43005#action_43005
]
Christian Schneider commented on CAMEL-527:
-------------------------------------------
I have only checked and compiled camel-core. There I changed all references to
CamelTemplate. If you say you want to keep CamelTemplate does this mean you
want to keep a copy of the DefaultProducertTemplate in camel named
CamelTemplate and mark this class as deprecated? I think this could be a good
thing. We could describe in the comments of the deprecated class how to get a
ProducerTemplate from CamelContext so people learn how they should chaange
their code.
> 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: 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 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.
