Congratulations Claus Ibsen and Jonathan Anstey for getting this book on paper. Camel is a framework which is truly a pleasure to work on. And it must be a very enjoyable exercise for you guys to theorize different aspects of it.
My question: While I was implementing an eventing API for an Enterprise Repository using asynchronous messaging as a transport, I faced multitude of issues related in writing Integration Tests using constructs in Camel Asynch API. Does the book cover the testing aspects for asynchronous messaging in depth? Secondly, are there any scenarios discussed in the book that caters to any similar testing reqmt as above?
Thanks very much.
Looking fwd to reading the book asap.
Joined: Apr 01, 2004
The source code for the book is 95% unit tests so there are plenty of testing examples.
Chapter 10 covers asynchronous routing and the source code shows some unit tests with that.
Chapter 6 covers testing and also integration testing.
Integration testing is of course more complex than unit testing as it often involves real live system you test against.
True, Integration tests, particularly in asynch scenarios many a times, have to resort to thread wait/notify or similar inter-thread communication solutions but with it there is always risk of missing messages in case of multiple routes, messages, predicates. Not sure if the new version of Camel is catering to any specific constructs so required in this area.