best practices for custom Exceptions
Posted on 2013-02-05
Is it good/normal practice to call another class to do something from inside a customException?
I want to clearly identify to an executive thread when something goes wrong in a weblogic producer class. I was thinking about uniquely catching all the various JMS exceptions, but want to throw one unique exception identifying that the weblogic interface has encountered a problem. I was thinking about defining and throwing a custom exception, and inside that class notifying the executive/main class to do some things? Is this the correct methodology?