0

I have a situation where I want to be able to distinguish between different types of errors within a web service. In an API this would usaully be a separate exception for each, does this mean I should have multiple fault contracts in WCF?

Is this the preferred approach, it seems the OO way to do it. Someone at my work suggested error codes but I'm starting to think it seems counter-intuative if you are sending an exception back.

Has anyone ever been in a similar situation, if so, what design decisions did you undertake and reasons for them?

Thanks, any help would be greatly appreciated. Jamie

Jamie
  • 876
  • 1
  • 10
  • 28

2 Answers2

1

Having different fault contracts is the way to go in WCF. Also centralizing the exception handling code in a custom error handler is a good idea. This way you no longer need to write all those try/catch and in the catch clause transform the exception into a fault contract in all service operations.

Darin Dimitrov
  • 1,023,142
  • 271
  • 3,287
  • 2,928
1

I agree Darin.

Have a look at:

WCF Error Handling without fault contract

It's very similar to your problem.

for more information:

http://www.c-sharpcorner.com/UploadFile/ankithakur/ExceptionHandlingWCF12282007072617AM/ExceptionHandlingWCF.aspx

Community
  • 1
  • 1
Massimiliano Peluso
  • 26,379
  • 6
  • 61
  • 70