I'm currently looking into the exception handling mechanism provided by Struts. Neat stuff really, because it hides exception handling logic that is not directly related to the business logic.
One of the goals in developing my current application is to make things simple and reduce the number of classes that I have to maintain. I've leveraged DispatchAction and DynaActionForm and it has worked great so far. The exception handling mechanism provided by Struts seemed like a good candidate to further simplify my application. I looked at org.apache.struts.action.ExceptionHandler and found that it caters to AppException. That is, if my application exceptions are extensions of AppException, I never really need to create any physical XXXXExceptionHandler objects, I can just use org.apache.struts.action.ExceptionHandler. My point of contention here is that AppException is dependent on ActionError which depends on ActionMessage. All of these are in the Struts framework. Now, if my application exceptions which are propogated from the business tier (which contains reusable business components) extend AppException, I have just loosely coupled my business tier to the Struts framework. I was wondering if these classes might eventually be moved into org.apache.commons module? Am I being too anal about this? Am I missing something? I have a solution staring me in the face and it seems that I may be avoiding it on principle. Any advice would be welcome. robert -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
