RE: Creating customer Exception class

["Clapham, Paul" <pclapham@xxxxxxxxxxxxx>]

No, that sounds like a reasonable design. But it would be possible to have 
"e.getMessage()" return the application's error message and 
"e.getCause().getMessage()" return the actual error message. The difference 
between that design and your proposed design is what happens when your 
customized Exception gets handled by some generic code (e.g. error logging) 
that only handles Exception. That code can't call your customized 
appLevelMessage method. So if you have such a thing, then it depends on how you 
want that code to behave.

PC2

-----Original Message-----
From: java400-l-bounces+pclapham=core-mark.com@xxxxxxxxxxxx 
[mailto:java400-l-bounces+pclapham=core-mark.com@xxxxxxxxxxxx] On Behalf Of Lim 
Hock-Chai
Sent: February 9, 2005 14:53
To: Java Programming on and around the iSeries / AS400
Subject: RE: Creating customer Exception class

Yes.  There is already a message field in the Exception class.  The reason that 
I want to create an additional appLevelErrMsg is because I want to retain 
everything that is in Exception.  appLevelErrMsg is more for what the user will 
see.  The message in Exception class is the actual error message that could 
help programmer debugging problem.  Do you think that is redundant?