tag:blogger.com,1999:blog-15701809.post2780929956983131771..comments2009-03-01T19:20:24.497+05:30creed - Uchithahttp://www.blogger.com/profile/10323105270454228259noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-15701809.post-72335689513619944242009-03-01T03:30:00.000+05:302009-03-01T03:30:00.000+05:30Hello Uchitha, <BR/>It is a nightmare to develop a nicely structured(less coupling) component without having "checked" exceptions. According to my experience, Java is more flexible than .net by having both types of exceptions. There are "must" handle exceptions within the block of code and if you throw them unchecked, there is no guarantee that you will handle them in proper way. Doesn't it destroy the whole idea of cohesion in OOP? The solution for the problems you pointed out (scalability and versioning) is to have user defined exceptions. That is the way to go! Define your own exception to handle most common, trivial exceptions and throw them up to the call stack, but handle/throw the "must handle" exceptions inside the same class/component.SMP(SiMPle) Shehanhttp://www.blogger.com/profile/06910985113761748664noreply@blogger.com