|
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? -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of Clapham, Paul Sent: Wednesday, February 09, 2005 3:18 PM To: Java Programming on and around the iSeries / AS400 Subject: RE: Creating customer Exception class But now that I look through the API documentation some more, I see there's already a (1.4) constructor "new Exception(String message, Throwable cause)"; you could just override Exception and use that constructor and your work would be done. PC2
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.