You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2012/07/12 10:07:34 UTC
[jira] [Created] (CAMEL-5440) mock endpoint should not add the
expect header check task every time we call the expectedHeaderReceived()
Willem Jiang created CAMEL-5440:
-----------------------------------
Summary: mock endpoint should not add the expect header check task every time we call the expectedHeaderReceived()
Key: CAMEL-5440
URL: https://issues.apache.org/jira/browse/CAMEL-5440
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.10.0
Reporter: Willem Jiang
Assignee: Willem Jiang
Fix For: 2.10.1, 2.11
If the message header value can just be consumed once, the mockEndpoint will complain the header value is null in second check, even the header value is checked rightly once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5440) mock endpoint should not add the
expect header check task every time we call the expectedHeaderReceived()
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-5440.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.9.3
Applied patch into trunk, camel 2.10.x and camel 2.9.x branch.
> mock endpoint should not add the expect header check task every time we call the expectedHeaderReceived()
> ---------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5440
> URL: https://issues.apache.org/jira/browse/CAMEL-5440
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.0
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> If the message header value can just be consumed once, the mockEndpoint will complain the header value is null in second check, even the header value is checked rightly once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira