Differentiate between business and technical fault

[camunda]

Hey guys.

A question more for best practice usage: Is there any built in support or preparation to distinguish business and technical faults? Normally you always have either business faults (which must be handled by e.g. the business process) and technical fault (which often are temporary and must be handled by an admin/monitoring and should NOT influence the business process).

Currently in an esb service I can only have one fault-to adress so send a faulted message, right? Any spontaneous thoughts at it?

Or do you think it is the responsibility of the service consumer to make that decision?

Cheers
Bernd

[kdeboer]

Hi Bernd,

In our case we have implemented a bridge btetween jbpm and jboss esb which does exactly this. We are able to define technical or business fault transiations which will/can be taken based upon the outcome of the service.We did create a dedicated 'service router' for this which reads the Ãnstructions'from the jms gateway and afterwards informs jbpm of the outcome.

Karl

[camunda]

Hi Karl.

We did this in another project as well, but there we changed quite a lot in the integration (almost a complete rewrite). tried to avoid that in the current project ;-)

But what would be really interessting: How do you define exactly, what is a technical and what a business fault?

Thanks Cheers
Bernd