Thanks Claus
Makes much more sense now, when you know the overrides.
For completeness sake I just move the header test like ->
public void testSomething() throws Exception {
String xmlFile = FileUtils.readFileToString(new
File("src/test/data/good.xml"));
M
Hi
I have updated the javadoc of the mock endpoint to better explain this.
On Thu, Apr 23, 2015 at 1:59 PM, Preben.Asmussen wrote:
> ahh - so expectedMessageCount and expectedHeaderValuesReceivedInAnyOrder
> exclude each other. Thats a bit unexpected. I would have guessed that all
> expectation
ahh - so expectedMessageCount and expectedHeaderValuesReceivedInAnyOrder
exclude each other. Thats a bit unexpected. I would have guessed that all
expectations set up in a test would have been evaluated.
Best,
Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Strange-
On Thu, Apr 23, 2015 at 1:24 PM, Preben.Asmussen wrote:
> Hi
>
> I'm experiencing some side effects when using
> expectedHeaderValuesReceivedInAnyOrder in a testcase.
>
> The following test will result in a ArrayOutOfBoundsException :
>
> public void testResultingInArrayOutOfBoundsException() thro
