[ https://issues.apache.org/jira/browse/CAMEL-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661863#comment-13661863 ]
Claus Ibsen commented on CAMEL-6377: ------------------------------------ Ad 1) I think the API names for - org.apache.camel.processor.CamelInternalProcessor - org.apache.camel.processor.CamelInternalProcessorTask is open for suggestions for new names. They were named *internal* by purpose to indicate its for internal use only. We can ponder about this for a bit. > Optimize routing engine to reduce stack frames in use during routing and > reduce callbacks > ----------------------------------------------------------------------------------------- > > Key: CAMEL-6377 > URL: https://issues.apache.org/jira/browse/CAMEL-6377 > Project: Camel > Issue Type: Improvement > Components: camel-core > Affects Versions: 2.12.0 > Reporter: Claus Ibsen > Assignee: Claus Ibsen > Fix For: 2.12.0 > > > We can optimize the Camel routing engine internally, and redue the need for > wrapping processors (those internally used for cross cutting functionality) > where they would wrap each other one by one; which then results in larger > call stacks during routing. > This also shows to end users when stacktraces is being logged etc, as they > tend to be a bit longer with many internal calls. > Though the JVM optimizes this at runtime as it can inline the calls and > whatnot. But the stacktraces is still shown expanded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira