camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Updated: (CAMEL-1078) Do not copy Exchanges at each step to improve performance
Date Thu, 25 Jun 2009 08:59:36 GMT


Claus Ibsen updated CAMEL-1078:

    Fix Version/s:     (was: 2.1.0)

Hadrian there are only 2-3 left so lets get them done before 2.0 is final.

That would be great as then there are no API changes needed for the performance improvements
we can do under the covers.

We could even consider making DefaultExchange *final* so people wont create their own classes.
Then the copy can be avoided.

> Do not copy Exchanges at each step to improve performance
> ---------------------------------------------------------
>                 Key: CAMEL-1078
>                 URL:
>             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.0.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.

View raw message