tag:blogger.com,1999:blog-61284219411416485862009-09-21T21:11:52.180-04:00Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6128421941141648586.post-6845664633792410302006-09-18T10:13:00.000-04:002006-09-18T10:59:21.795-04:00

Sven Heyll responded to my difficulties with mock objects and unit tests here:The purpose of the MOCKAfter finishing my JDBC-related code, I spent the last two weeks furiously implementing some higher-level code which did not rely on JDBC, and re-examined my usage of mock objects once again. As Sven indicates in his post, I missed the point the first time around. Sven explains that mock objects

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com0tag:blogger.com,1999:blog-6128421941141648586.post-67509434233080444722006-09-01T13:06:00.000-04:002006-09-01T13:09:02.756-04:00

This is a few months old, but it's the first time I've seen it, and it's certainly an appropriate follow-up to the previous post. Dave Astels talks about BDD and rSpec.http://video.google.com/videoplay?docid=8135690990081075324&q=test

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com0tag:blogger.com,1999:blog-6128421941141648586.post-77994944278489417832006-08-31T10:06:00.000-04:002006-08-31T10:41:25.755-04:00

I realized something about the unit tests I had been writing today: I couldn't change even a line of the code they were testing without changing the tests themselves as well. Now, I understand that unit tests always carry some maintenance overhead, and will need to be udpated from time to time as a system's design evolves. But unit tests are also supposed to enable refactoring by ensuring that

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com2tag:blogger.com,1999:blog-6128421941141648586.post-24374781903531345732006-08-25T10:22:00.000-04:002006-08-25T12:28:28.884-04:00

I recently struggled with getting XA transactions to work across Oracle 9i and SQL Server 2000 databases, using a combination of Hibernate, Spring, JOTM, and the SQL Server 2005 JDBC driver. I ran into some stickiness, and I still think I might be missing something - but XA transactions work. Recovery probably doesn't, but for our organization that's OK right now. In the off-chance that my

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com0tag:blogger.com,1999:blog-6128421941141648586.post-53574896917347924802006-08-15T11:37:00.000-04:002006-08-15T11:44:02.307-04:00

We're using Maven 2 here to manage our build process, and I'd like to make the maven-generated site our main source for developer documentation since it already hosts reports, JavaDocs, etc. Unfortunately, the site plug-in (currently at version 2.0-beta-5 I believe) is not exactly being cooperative. I have some menus defined in site.xml for the top-level project which I do not want inherited by

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com0tag:blogger.com,1999:blog-6128421941141648586.post-26214184071284369042006-08-15T11:25:00.000-04:002006-08-15T11:31:00.916-04:00

Blogs often contain information of no relevance to anyone but the blogger/blogger's immediate circle, and I've held out for fear of adding to the noise. Until now, that is. Java- and developer-related blogs have recently pulled me out of a couple jams, so to return the favour I'll document my difficulties here on the web for the benefit any fellow developers struggling with Java, Hibernate,

Matt McGillhttp://www.blogger.com/profile/18441137187749531655noreply@blogger.com0