This content has been marked as final.
Show 19 replies
-
15. Re: How to stop the pipeline process and return an error mes
kconner Jun 19, 2007 9:15 AM (in response to claudio_br)Hiya Claudio.
Update the code from subversion and rebuild the distribution. -
16. Re: How to stop the pipeline process and return an error mes
claudio_br Jun 19, 2007 10:36 AM (in response to claudio_br)Hi Kevin,
I updated my ESB.
The problem with RelatesTo was resolved.
But when I am usingthrow new ActionProcessingFaultException("my exception");
I get only the the fault´s reason (String of exception).
When I am usingthrow new ActionProcessingFaultException(message,"my exception");
I get a (customize) message with more detail about errors.
There is a way to catch exception throw in pipeline from message.getFault() (ActionProcessingFaultException("my exception"))? or only through ActionProcessingFaultException(message,"my exception")?
Thanks
-
17. Re: How to stop the pipeline process and return an error mes
marklittle Jun 19, 2007 2:18 PM (in response to claudio_br)"claudio_br" wrote:
But when I am usingthrow new ActionProcessingFaultException("my exception");
I get only the the fault´s reason (String of exception).
That's because you have not associated a fault Message with the exception. That is optional, but if you don't provide a Message then a default one will be created by the ESB and returned using the rules defined in the documentation. That default Message will only be able to contain information from the exception (the 'cause' in this case).
When I am usingthrow new ActionProcessingFaultException(message,"my exception");
I get a (customize) message with more detail about errors.
Yes, in this case the ESB will return the Message you provide within the exception. The current implementation actually ignores any other information within the exception (e.g., the 'cause') under the assumption that the Message contains everything (which it really should do).
There is a way to catch exception throw in pipeline from message.getFault() (ActionProcessingFaultException("my exception"))? or only through ActionProcessingFaultException(message,"my exception")?
You can throw other exceptions, but as I've said elsewhere in this thread, ActionProcessingFaultException is the way you should go to get control over what Message is returned and to whom. -
18. Re: How to stop the pipeline process and return an error mes
claudio_br Jun 19, 2007 2:48 PM (in response to claudio_br)Ok Mark,
The development team could add to an example in quickstart with this case
Thank you for your attention. -
19. Re: How to stop the pipeline process and return an error mes
marklittle Jun 20, 2007 4:49 AM (in response to claudio_br)"claudio_br" wrote:
Ok Mark,
The development team could add to an example in quickstart with this case
Thank you for your attention.
Or you could contribute one ;-)