<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SOA component design: thinking about error handling</title>
	<atom:link href="http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/</link>
	<description>A weblog about software engineering, Architecture, Technology an other things we like.</description>
	<lastBuildDate>Thu, 19 Aug 2010 21:06:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Eric Elzinga</title>
		<link>http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/comment-page-1/#comment-3398</link>
		<dc:creator>Eric Elzinga</dc:creator>
		<pubDate>Sat, 02 Aug 2008 20:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/#comment-3398</guid>
		<description>Hi Ben,

I&#039;m doing a lot integration projects lately and we noticed implementing good eror handling functionality takes a lot of time. Mostly these parts are also not well planned in the projects. For integration components it&#039;s hard to have good error handling functionality because reaches a lot of components and environments. Every possible error can also have it&#039;s own  handling functionality. Integration components like bpels could make use of compensation handlers but in java you would try to handle it which the exceptions, and other components could have their own strategies for those situations. So...it&#039;s hard to describe one generic error handling strategy which applies all.But for sure it&#039;s important to &#039;think more&#039; about error handling&#039; :)</description>
		<content:encoded><![CDATA[<p>Hi Ben,</p>
<p>I&#8217;m doing a lot integration projects lately and we noticed implementing good eror handling functionality takes a lot of time. Mostly these parts are also not well planned in the projects. For integration components it&#8217;s hard to have good error handling functionality because reaches a lot of components and environments. Every possible error can also have it&#8217;s own  handling functionality. Integration components like bpels could make use of compensation handlers but in java you would try to handle it which the exceptions, and other components could have their own strategies for those situations. So&#8230;it&#8217;s hard to describe one generic error handling strategy which applies all.But for sure it&#8217;s important to &#8216;think more&#8217; about error handling&#8217; <img src='http://www.gridshore.nl/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jettro</title>
		<link>http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/comment-page-1/#comment-2926</link>
		<dc:creator>jettro</dc:creator>
		<pubDate>Sun, 27 Jul 2008 06:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/07/26/soa-component-design-thinking-about-error-handling/#comment-2926</guid>
		<description>Nice one again Ben. I think a good error handling strategy for projects and frameworks is overlooked a lot. This is often done as one of the last things, when it is to late and no real strategy is used at all. A good way of noticing this is a lot of catch RuntimeException/Exception in the code.

I am running into the same problem with flex, there is also a fault mechanism with events implemented. But you do not have the capabilities of java available to handle the events in a standard way. You can create a mechanism yourself, but for bigger appications that is not what you want.

Error handling keeps being one of 4 attention points for projects: configuration management, application layering, standardized package, class and method names and error handling.

thanks for the article.</description>
		<content:encoded><![CDATA[<p>Nice one again Ben. I think a good error handling strategy for projects and frameworks is overlooked a lot. This is often done as one of the last things, when it is to late and no real strategy is used at all. A good way of noticing this is a lot of catch RuntimeException/Exception in the code.</p>
<p>I am running into the same problem with flex, there is also a fault mechanism with events implemented. But you do not have the capabilities of java available to handle the events in a standard way. You can create a mechanism yourself, but for bigger appications that is not what you want.</p>
<p>Error handling keeps being one of 4 attention points for projects: configuration management, application layering, standardized package, class and method names and error handling.</p>
<p>thanks for the article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
