Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
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.
Attachments
Issue Links
- links to