The Action handles flow-control, and selects page displays, including error pages. Actions should be prepared to cope with whatever exceptions are thrown, either directly or with an ancestor method. See also < http://www.mail-archive.com/[email protected]/msg09256.html > and < http://www.mail-archive.com/[email protected]/msg08930.html > -- Ted Husted, Husted dot Com, Fairport NY USA. -- Custom Software ~ Technical Services. -- Tel 716 737-3463. -- http://www.husted.com/about/struts/ Seth Riney wrote: > Had a question regarding the best practice of handling non-Servlet or > IOExceptions in Actions. Better to > a) subclass Action, > b) catch each exception and throw it as a generic Exception > c) create an ActionErrors object and pass around stack traces > that way. > > Any thoughts would be greatly appreciated.
