I prefer this "elaborate" approach. (And I liked your inclusion of an InterruptedHttpException.) I don't think the dependency on commons-lang is really required, though. If we want to avoid it, we can just put the nesting support into our own root HttpException class. The only parts that are really required are a field to hold the nested exception, a couple of constructors, and an accessor for the nested exception. Of course, a few convenience methods would be nice too.2) Go elaborate ----------------- org.apache.commons.lang.exception.NestableException (or equivalent) | +-- org.apache.commons.httpclient.HttpException (Root exception)
Personally, I'm fine with a dependency on commons-lang; I just wanted to throw out an alternative if there turn out to be people who aren't.
-- Laura
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
