camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1078) Do not copy Exchanges at each step to improve performance
Date Thu, 14 May 2009 15:24:50 GMT

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

Hadrian Zbarcea commented on CAMEL-1078:
----------------------------------------

@Roman,
I will work on finishing this issue this week, so we could have it in 2.0-M2.  I am not sure
I agree with the no specialized Messages proposal, I hope others will pitch in.  I think it's
actually a "cleaner" solution than you "dirty" flag (sorry, couldn't resist it :) ).


> Do not copy Exchanges at each step to improve performance
> ---------------------------------------------------------
>
>                 Key: CAMEL-1078
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1078
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.5.0
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> The code in DefaultEndpoint.createExchange(Exchange exchange), calls on getExchangeType()
to figure out if a new copy of Exchange needs be created.  The code relies though on the generic
argument of the Endpoint type to figure out the actual Exchange type.  With the generics removed
part of CAMEL-872, getExchangeType() always returns null, forcing a copy every time.
> There is no real need to extend Exchange, so the proposal for this to make the Exchange
final and move the component specific bits, if any,  in the Message.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message