Why don't you throw the exception from the Data Access class and catch it in DispatchAction and if there is an exception then forward to the error jsp page else to the display jsp?
-----Original Message----- From: Yee, Richard K,,DMDCWEST [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 3:22 PM To: 'Struts Users Mailing List' Subject: RE: [OT] Handling database connection exceptions Shyam, Where in your JSP does the NullPointerException occur? Is it in a method call in a scriptlet? If so, your JSP is still indirectly accessing the database. What Wendy suggested was that the the database access class be invoked from your DisplactAction class and the results be put in a collection and set as an attribute in the request. That way, any problems with getting the data would be caught in your Action class and then you could forward to an error page. Otherwise, why can't you just specify an error page using the errorPage attribute in your JSP's <[EMAIL PROTECTED] ...> tag? -Richard -----Original Message----- From: Shyam A [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 3:10 PM To: Struts Users Mailing List Cc: [EMAIL PROTECTED] Subject: RE: [OT] Handling database connection exceptions Wendy, Thanks for your mail. I don't know if you fully understood where I'm coming from! As I said, the database connection is accessed from a Data Access class (read model), which is called from my DispatchAction class. Since the exception is not caught in my DispatchAction class (the methods throw Exception), it is propagated to my JSP's. It doesn't mean my JSP's directly access the database! Anyway, thanks for your help. Shyam --- Wendy Smoak <[EMAIL PROTECTED]> wrote: > > I have a Database servlet configured in web.xml, > which > > intialises a connection pool on Server startup. > > However, if the data source is unavailable, I get > a > > "Null Pointer" exception on my JSPs, which is > > propagated from my Data Access class. > > IMO, the problem is that you're accessing the > database from the JSP. > And this, in a Struts webapp?! The view has no > business talking to the > model. > > If you move the data access to the Action, then you > can catch the error > and gracefully forward to an error page. > > Meanwhile, you can define error pages in web.xml so > that your users > don't see the stack trace. For example, I have > this: > <error-page> > > <exception-type>javax.servlet.ServletException</exception-type> > > <location>/WEB-INF/jsp/exceptionServlet.jsp</location> > </error-page> > which gives the user an apology and a phone number > to call. > > -- > Wendy Smoak > Applications Systems Analyst, Sr. > Arizona State University, PA, IRM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]