You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/09/02 04:47:00 UTC

[jira] [Updated] (CAMEL-16905) camel-mock - Remove old code that checks for header values as Expression/Predicate

     [ https://issues.apache.org/jira/browse/CAMEL-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-16905:
--------------------------------
    Fix Version/s:     (was: 3.x)
                   3.12.0

> camel-mock - Remove old code that checks for header values as Expression/Predicate
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-16905
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16905
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Karen Lease
>            Priority: Major
>             Fix For: 3.12.0
>
>
> 1. For consistency in testing, it seems like
> MockEndpoint.extractActualValue() should also not evaluate the Expression.
> Also it looks like CAMEL-1848 may be added before we had a better way
> for mock endpoints to do assertions.
> The use case seemed to be to provide an XPathBuilder (expression) as a
> value that then is used to match against the real value.
> Today you can setup
> mock.message(0).header("foo").matches(xpath("...")) (something like
> that)
> So I would assume we could look at remove that ancient code from the
> mock component.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)