TBO code: Handling non-DFC errors on doSave()?

What is the recommended practice for handling non-DFC errors that occur in TBO code?

Specifically - on doSave() and doCheckin() methods. These methods will throw only DfExceptions not the generic Exception.

Do you:

- create a custom DfException with the error and throw that back?

- just log the non-DFC exception.

Thanks for all replies!

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

bacham2

Unless the calling applications plan to handle these exception differently than DFC errors, I see no reason for the overhead of an addional exception class.

Keep it simple!

Hicham

All comments

Francois Dauberlieu

I'd go for 1. However, I'd also log the error

Trupthy.Bharadwaj

Thanks, Francois! That's what I was thinking too

bacham2

Unless the calling applications plan to handle these exception differently than DFC errors, I see no reason for the overhead of an addional exception class.

Keep it simple!

Hicham

Francois Dauberlieu

Good point, you're right

Trupthy.Bharadwaj

Ok - so based on your suggestions (thanks Francois and Hicham!), I decided to:

- throw a new DF exception with a message similar to "Error on doSave(). Check log for details." The log file will have the entire stack trace.

Hicham - yes, you are right, teh calleing applications are not going to handle DFC and non DFC exceptions (or any exception) differently.

Thanks for all the replies!