Isn't it because code that uses the exceptions
for business logic might need to rely on the original exception
type?
E.g., the client might rely on getting specific
exceptions like ...
try
{
DomainModel.CreateBanana("banana name", "banana
description");
}
catch(DuplicateBananaException
dbne)
{
MessageBox("There is
already a banana called " + dbne.DuplicateBanana.Name);
}
Sent: Saturday, January 26, 2008 11:38 PM
Subject: Re: [NHibernate-development] NHibernate proxies losing
exceptionstack-trace
Is there any reason to go with this approach over simply throwing
a HibernateException() with this as the inner exception?
-------------------------------------------------------------------------
This
SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R)
Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nhibernate-development
mailing
list
Nhibernate-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nhibernate-development