I don't see a problem, other than that you can't rely on the nested exception being serializable. That can cause some weirdness when you try to serialize the exception and get an exception. Perhaps adding some code to check for that, and not attempting to serialize a non-serializable exception?
On Thursday 07 November 2002 07:16 am, Steven Caswell wrote: > Is there any objection to making the Nestable exception classes > serializable? Any particular issues that should be addressed? I'll be > happy to make the changes if there is no objection. > > > Steven Caswell > [EMAIL PROTECTED] > "In our own native land, in defense of the freedom that is our > birthright, and which we ever enjoyed till the late violation of it -- > for the protection of our property, acquired solely by the honest > industry of our fore-fathers and ourselves, against violence actually > offered, we have taken up arms. We shall lay them down when hostilities > shall cease on the part of the aggressors, and all danger of their being > renewed shall be removed, and not before." - Thomas Jefferson -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
