You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/06/28 17:53:16 UTC
[jira] [Updated] (CAMEL-4160) MockEndpoint - Add options to only
keep X first / last messages
[ https://issues.apache.org/jira/browse/CAMEL-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-4160:
-------------------------------
Comment: was deleted
(was: Okay I have this working now. Will polish it a bit as I noticed we should try to type coerce the expected bodies.)
> MockEndpoint - Add options to only keep X first / last messages
> ---------------------------------------------------------------
>
> Key: CAMEL-4160
> URL: https://issues.apache.org/jira/browse/CAMEL-4160
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
>
> If you use mock endpoints they keep a copy of the exchange send to it. But if you test using a lot of messages (eg lets say 500.000) then that takes up much memory.
> So in some cases it may be desireable to just say only keep X number of messages (keepFirst=10&keepLast=10) to keep the first 10 and last 10 messages.
> The name of the options could maybe be something more appropriate.
> When using these options there may be some assertions that is not possible. But thats an acceptable tradeoff when you just want to use mocks to say, okay I expect at least 250000 messages here. And the first message should be like this, and the last message should be like that. etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira