[
https://issues.apache.org/jira/browse/CAMEL-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099033#comment-13099033
]
Hadrian Zbarcea commented on CAMEL-4417:
----------------------------------------
@Christian, all the changes you make in 2.9 should be backwards compatible. So
if you make any changes, please make sure leave existing classes in place (even
as extensions of refactored classes) and change as few tests as possible,
ideally none. That ensures two things: one that we didn't break anything and
existing code still works, second that users have a migration path that could
take at any time. We can remove the old classes later in 3.0.
Changes that break backward compatibility I'd leave for later.
> Move base classes used by components from impl to support
> ---------------------------------------------------------
>
> Key: CAMEL-4417
> URL: https://issues.apache.org/jira/browse/CAMEL-4417
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.8.0
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
> Attachments: CAMEL-4417-1.patch
>
>
> Several classes in impl are used or extended by components. We should avoid
> this.
> The base classes should be moved to support. Examples are DefaultComponent,
> DefaultEndpoint, DefaultProducer.
> Another case is the AsyncProcessorTypeConverter. The typeconverter is well
> placed in impl but the class also has a public static convert method that is
> used from many components. So this functionality should be moved to processor
> so it is available to components.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
