  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
  | | | Exception Handling in J2EE project | Exception Handling in J2EE project 2003-12-08 - By Prasenjit Narwade
Back Hi All, What is the best Hierarcy (framework) for handling exceptions in a J2EE project.
I am thinking of some roughly the following Hierarcy consisting broadly of three categories :
+ MyApplicationException extends Exception ( For handling bussiness exceptions.) - InsufficientBalanceException - InvalidPasswordException - etc.
+ MySystemException extends RuntimeException (Non bussiness exception, exception due to System problems)
+ MyEJBException extends EJBException (Not too sure if this is required)
My question is :
1. Is this approach correct ?
2. My application flow consists of ActionClass calls BussinessDelegate calls SessionBean calls DAO and ActionClass calls BussinessDelegate calls SessionBean calls EntityBeans
How should the exception for take place. Should it be something like this:
DAO throws some ApplicationException ... caught by SessionBean thrown as some EJBException ...... caught by BussinessDelegate and do some handling
Regards, Prasenjit.
==================================================================== Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |