tag:blogger.com,1999:blog-34908752.post7618751480749053338..comments2010-06-07T00:50:18.619+01:00Steve Freemanhttp://www.blogger.com/profile/14771999065792016571noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-34908752.post-44522846951316806392009-09-11T13:20:23.900+01:002009-09-11T13:20:23.900+01:00Minor correction for you - &quot;using the new Proxy type in Java 1.1&quot; - Proxy was introduced in Java 1.3<br /><br />I know this because MockMaker (a mock object code generator used at Connextra before &quot;Another Generation&quot;) had to use code generation as we were using VisualAge for Java at Connextra which only supported Java 1.1.8 (or thereabouts) at the time.Ivan Moorehttp://www.blogger.com/profile/09119134602348298270noreply@blogger.comtag:blogger.com,1999:blog-34908752.post-11001364576205128832009-09-09T22:16:45.710+01:002009-09-09T22:16:45.710+01:00@Jonas. Thanks. One of our great frustrations has been how the concept has been so misunderstood -- largely because our own early misconceptions seem to have been the ones that spread. It takes a little effort and experience to learn to see where to put the seams.Steve Freemanhttp://www.blogger.com/profile/14771999065792016571noreply@blogger.comtag:blogger.com,1999:blog-34908752.post-22629703940636863012009-09-09T08:09:12.657+01:002009-09-09T08:09:12.657+01:00Thanks for a very nice read!<br /><br />&gt;<i>the critical idea was that the technique emphasizes the roles that objects play for each other</i><br /><br />I really like this idea but it hasn&#39;t been totally obvious to me working with mock objects on my own or in code written by others. Often the mocking has been quite implementation specific and done on the lowest level possible.Jonas Elfströmhttp://www.blogger.com/profile/18088865137364783994noreply@blogger.com