<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: LegStar for Mule Patterns</title>
	<atom:link href="http://blogs.mulesoft.org/legstar-for-mule-patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.mulesoft.org/legstar-for-mule-patterns/</link>
	<description>Musings from the MuleSoft Experts</description>
	<lastBuildDate>Thu, 09 Sep 2010 13:52:50 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Fady</title>
		<link>http://blogs.mulesoft.org/legstar-for-mule-patterns/comment-page-1/#comment-3099</link>
		<dc:creator>Fady</dc:creator>
		<pubDate>Sun, 23 Aug 2009 13:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mulesource.org/?p=823#comment-3099</guid>
		<description>Integrating mainframes with Legs4Mule rather than specialized servers has 2 major advantages in my opinion: 
First is the open source nature of the tools, LegStar for Mule is completely open source, including developers tools. It is free for download by anyone and is licensed under the liberal LGPL. I am not aware of any so called Connectors that are open source.
Second are the economy of scale that can be achieved by leveraging an ESB core integration capabilities. Transforming XML to CSV is not different from transforming a mainframe data buffer to a java object; so why should we deploy such transformers differently or run them in different complex multi-threaded servers? With LegStar for Mule, developers and administrators have a single platform to learn: the ESB.</description>
		<content:encoded><![CDATA[<p>Integrating mainframes with Legs4Mule rather than specialized servers has 2 major advantages in my opinion:<br />
First is the open source nature of the tools, LegStar for Mule is completely open source, including developers tools. It is free for download by anyone and is licensed under the liberal LGPL. I am not aware of any so called Connectors that are open source.<br />
Second are the economy of scale that can be achieved by leveraging an ESB core integration capabilities. Transforming XML to CSV is not different from transforming a mainframe data buffer to a java object; so why should we deploy such transformers differently or run them in different complex multi-threaded servers? With LegStar for Mule, developers and administrators have a single platform to learn: the ESB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://blogs.mulesoft.org/legstar-for-mule-patterns/comment-page-1/#comment-3094</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Thu, 20 Aug 2009 21:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mulesource.org/?p=823#comment-3094</guid>
		<description>I am relatively new to the industry an by no means an expert but isn&#039;t it true that  &lt;a href=&quot;http://www.pervasiveintegration.com/data_connectors/Pages/legacy_data_integration.aspx&quot; rel=&quot;nofollow&quot;&gt;legacy integration&lt;/a&gt; to many vendors is anything that was here before we arrived?
I was reading you article on the Mule system and have been broadening my view of the industry and I wanted to know what makes integrating the mainframe with mule any better than any other brand/company out there? Are they all pretty much the same with different packaging and price. And do most come with the &lt;a href=&quot;http://www.pervasiveintegration.com/data_connectors/Pages/data_connectors.aspx&quot; rel=&quot;nofollow&quot;&gt;connectors&lt;/a&gt; you need to communicate between the applications and mainframe???</description>
		<content:encoded><![CDATA[<p>I am relatively new to the industry an by no means an expert but isn&#8217;t it true that  <a href="http://www.pervasiveintegration.com/data_connectors/Pages/legacy_data_integration.aspx" rel="nofollow">legacy integration</a> to many vendors is anything that was here before we arrived?<br />
I was reading you article on the Mule system and have been broadening my view of the industry and I wanted to know what makes integrating the mainframe with mule any better than any other brand/company out there? Are they all pretty much the same with different packaging and price. And do most come with the <a href="http://www.pervasiveintegration.com/data_connectors/Pages/data_connectors.aspx" rel="nofollow">connectors</a> you need to communicate between the applications and mainframe???</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Braasch</title>
		<link>http://blogs.mulesoft.org/legstar-for-mule-patterns/comment-page-1/#comment-3017</link>
		<dc:creator>Bill Braasch</dc:creator>
		<pubDate>Sat, 11 Jul 2009 18:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mulesource.org/?p=823#comment-3017</guid>
		<description>what Craig said.  Mainframes are not going away, but they do speak their own language.  You give a good explanation of the benefits of a common representation among the specialty skills that combine to build successful bridges.

Patterns, working models and good examples lead to more robust solutions.  Thanks for the LegStar project and for sharing your design with us.</description>
		<content:encoded><![CDATA[<p>what Craig said.  Mainframes are not going away, but they do speak their own language.  You give a good explanation of the benefits of a common representation among the specialty skills that combine to build successful bridges.</p>
<p>Patterns, working models and good examples lead to more robust solutions.  Thanks for the LegStar project and for sharing your design with us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Tataryn</title>
		<link>http://blogs.mulesoft.org/legstar-for-mule-patterns/comment-page-1/#comment-3013</link>
		<dc:creator>Craig Tataryn</dc:creator>
		<pubDate>Fri, 10 Jul 2009 15:25:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mulesource.org/?p=823#comment-3013</guid>
		<description>Excellent article Fady.  The more mainframe integration documentation you can put out, the better IMHO.  The fact of the matter is, the Main Frame is not going anywhere in the enterprises who have existing legacy systems.  So the better we can integrate with it, the better our overall solutions will become.</description>
		<content:encoded><![CDATA[<p>Excellent article Fady.  The more mainframe integration documentation you can put out, the better IMHO.  The fact of the matter is, the Main Frame is not going anywhere in the enterprises who have existing legacy systems.  So the better we can integrate with it, the better our overall solutions will become.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
