I’ve just read an article on exception handling antipatterns by Tim McCune over on java.net.
In thie article, Tim describes the different types of exceptions Java has and when each different type should be used. He then goes on to detail 12 antipatterns giving an example of each and explaining why the code is wrong.
This is an excellent article, and one I would recommend to any Java developer.
Thanks to this post on The Pragmatic Architect I’ve downloaded Sun’s Java Studio Enterprise with the intention of using it for UML modelling. I’ve only played with it so far, but it looks like a comprehensive UML modelling package. I’ll post some more notes when I’ve used it further.
I’ve just started working on a fairly small web application project that uses Struts as its web framework. I like Struts, its fairly simple to use and covers just about everything I need for my application.
Since I’m now using NetBeans 5 Beta 2 (eventually!), I though I would have a read of Geertjan’s series of articles on how to use Struts with NetBeans. These are good articles if you are new to Struts or want to see how NetBeans handles Struts development.
However, since I’ve used Spring in the past, Geertjan’s method of grabbing database connections seems odd. I’m not detracting in any way from the series of articles (which are great) which are intended to discuss struts development with NetBeans – this is more of a problem I have with Struts.
Once you get into the rhythm of using DI, it seems strange going back to explicitly setting things up. For example datasources – injecting datasources directly into DAOs is one of the best things that I like about Spring and something that seems completely unnecessary now when using Struts.
As patterns generally described good software practices, antipatterns do the opposite – they describe bad software practices.
Theres a good article on devx.com that gives an introduction to antipatterns.