You are correct that using specific implementation classes is completely appropriate in general. However, in this case, I would not be able to *easily* share the test code between the embedded and the client driver when running the JUnit test in our harness (I'm not very fond of the master based tests).
Hi Kristian,
Thanks for the explanation. Your plan seems good to me. thanks, bryan
