<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://coldfusion.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Mark van Hedel</title>
 <link>http://coldfusion.sys-con.com/</link>
 <description>Latest articles from Mark van Hedel</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Thu, 28 Aug 2008 14:08:46 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Designing ColdFusion Applications for Deployment as EAR Files</title>
 <link>http://coldfusion.sys-con.com/node/235995</link>
 <description>Enterprise Application aRchive (EAR) files are a standard and portable manner for packaging applications to be deployed on J2EE application servers, such as Adobe JRun, BEA WebLogic, and IBM WebSphere. An EAR file is, in essence, just a big ZIP file with a special layout of the directory tree inside that contains a full application, see the following code. EAR files have a well-defined format and make Java bytecode truly portable. The same EAR file that we compile and build on our i386 Windows laptop can also run on a 64-CPU mainframe running commercial Unix.&lt;p&gt;&lt;a href=&quot;http://coldfusion.sys-con.com/node/235995&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 19 Jul 2006 03:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://coldfusion.sys-con.com/node/235995</guid>
</item>
</channel>
</rss>
