You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/10/25 15:45:00 UTC
[jira] [Comment Edited] (CAMEL-15753) camel-core - Modularize move
some parts from camel-base to camel-support
[ https://issues.apache.org/jira/browse/CAMEL-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220284#comment-17220284 ]
Claus Ibsen edited comment on CAMEL-15753 at 10/25/20, 3:44 PM:
----------------------------------------------------------------
- ProcessorFactory to use Object[] instead of Map for custom args (faster)
- Other modules to depend on camel-core-processor instead of camel-base *DONE*
- camel-core-processor -> camel-core-model-processor so we have EIP processors in their own JAR and core processors in another JAR
was (Author: davsclaus):
- ProcessorFactory to use Object[] instead of Map for custom args (faster)
- Other modules to depend on camel-core-processor instead of camel-base
- camel-core-processor -> camel-core-model-processor so we have EIP processors in their own JAR and core processors in another JAR
> camel-core - Modularize move some parts from camel-base to camel-support
> ------------------------------------------------------------------------
>
> Key: CAMEL-15753
> URL: https://issues.apache.org/jira/browse/CAMEL-15753
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.7.0
>
>
> We have some parts in camel-base that may be better to move out as it may be used by end users as well, like some of the out of the box aggregation strategies.
> We may consider having camel-base as for internal implementation for camel-core. And if we can get things out of this to camel-support that may be used by end users we have a bit better modularization.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)