TapestryException is intented for use when there is a Location (or Locatable) object associated with the exception.
On Sun, Mar 29, 2009 at 1:58 PM, manuel aldana <[email protected]> wrote: > I am currently working on https://issues.apache.org/jira/browse/TAP5-423. > > For that I like to programm defensively, so am working a lot with > IllegalArgumentException for checking passed param to public methods or for > checking consisntency of classes internal code with asserts. > > Currently I am using IllegalArgumentException exclusively, but I noticed > that there is also TapestryException which is used in some occasions. What > is the convention for IllegalArgument vs. TapestryException when checking > things? > > > -- > manuel aldana > [email protected] > software-engineering blog: http://www.aldana-online.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
