tag:blogger.com,1999:blog-82799045248352799.post697703861880432240..comments2024-03-19T07:49:12.723+01:00Comments on Architect Consultant blog: Service Orientation: Exception handling patternRoger van de Kimmenadehttp://www.blogger.com/profile/04738763579441543087noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-82799045248352799.post-13338406017785297842010-09-28T11:05:56.684+02:002010-09-28T11:05:56.684+02:00Harald,
Thanks for the questions!
You can decide ...Harald,<br />Thanks for the questions!<br /><br />You can decide to expose an error in multiple ways. This is the same as deciding that capabilities are copied with different granularities. This way consumers have the option to choose.<br /><br />About the guideline:<br />- Hide technical errors as much as possible<br />- Expose functionel errors when really needed<br /><br />Other suggestions or guidelines are appreciated.<br /><br />Thx<br />RogerRoger van de Kimmenadehttps://www.blogger.com/profile/04738763579441543087noreply@blogger.comtag:blogger.com,1999:blog-82799045248352799.post-16995177289863983802010-09-28T10:23:29.900+02:002010-09-28T10:23:29.900+02:00Roger, thanks for these insights.
Some questions ...Roger, thanks for these insights.<br /><br />Some questions that come to mind:<br /> - Are the options how to expose an error mutual exclusive or is it possible that one error is (concurrently) exposed in multiple ways?<br /> - Is there a guideline how to either handle errors internally or how to expose them?Harald van der Weelhttps://www.blogger.com/profile/13352602368388711191noreply@blogger.com