<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Technical Blog</title>
    <link>https://grep.elasticpath.com/community/techblog/blog</link>
    <description />
    <pubDate>Fri, 23 Dec 2011 12:26:33 GMT</pubDate>
    <generator>Clearspace 2.5.7 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2011-12-23T12:26:33Z</dc:date>
    <item>
      <title>Fun with Camel</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/12/23/fun-with-camel</link>
      <description>When customizing Elastic Path the most common form of Java-code level customization is integration with an external fulfillment service.  This integration can take many forms, depending on your architecture:  SOAP or Restful Web services, JMS messages,</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">integration</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">camel</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">fulfillment</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">route</category>
      <pubDate>Fri, 23 Dec 2011 12:41:16 GMT</pubDate>
      <author>darren.pendery@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/12/23/fun-with-camel</guid>
      <dc:date>2011-12-23T12:41:16Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/fun-with-camel</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1158</wfw:commentRss>
    </item>
    <item>
      <title>Connect Subversion and Perforce with Git</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/12/12/connect-subversion-and-perforce-with-git</link>
      <description>git-svn, meet git-p4 Many developers have started to use Git, a distributed VCS that offers a lot of advantages over centralized repositories when it comes to team development.  This is further fueled by the success of the integration tool between Git</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">subversion</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">perforce</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">svn</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">p4</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">merge</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">branch</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">git</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">rebase</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">trunk</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">commit</category>
      <pubDate>Mon, 12 Dec 2011 20:49:10 GMT</pubDate>
      <author>roy.lim@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/12/12/connect-subversion-and-perforce-with-git</guid>
      <dc:date>2011-12-12T20:49:10Z</dc:date>
      <clearspace:dateToText>1 month, 4 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/connect-subversion-and-perforce-with-git</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1157</wfw:commentRss>
    </item>
    <item>
      <title>Excursions into Hash Code / Equals</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/10/06/excursions-into-hash-code-equals</link>
      <description>Introduction &amp;nbsp; Although at times the hashCode and equals methods seem to be a “no-glory” implementation, they are extremely important in maintaining correct data manipulation. Joshua Bloch's Effective Java has an excellent overview of the concerns</description>
      <pubDate>Thu, 06 Oct 2011 21:03:47 GMT</pubDate>
      <author>dave.baker@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/10/06/excursions-into-hash-code-equals</guid>
      <dc:date>2011-10-06T21:03:47Z</dc:date>
      <clearspace:dateToText>4 months, 4 days ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/excursions-into-hash-code-equals</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1155</wfw:commentRss>
    </item>
    <item>
      <title>Clustering Quartz Jobs</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/09/19/clustering-quartz-jobs</link>
      <description>Overview The standard Elastic Path Quartz jobs are tied to the JVM and are not distributed.    If configured on multiple servers they will be executed on multiple servers simultaneously.  The challenge is that jobs which update entities should not be</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">quartz</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">scheduler</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">jobs</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">clustering</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">cluster</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">clustered</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">distributed</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">reliability</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">persisted</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">factory</category>
      <pubDate>Mon, 19 Sep 2011 15:22:22 GMT</pubDate>
      <author>darren.pendery@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/09/19/clustering-quartz-jobs</guid>
      <dc:date>2011-09-19T15:22:22Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/clustering-quartz-jobs</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1154</wfw:commentRss>
    </item>
    <item>
      <title>A Look into Code Review Tools - Code Collaborator</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/09/13/a-look-into-code-review-tools--code-collaborator</link>
      <description>Code review is a good way to catch mistakes, review designs, and help developers learn from each other.  Over-the-shoulder reviews are an easy habit to enforce for small teams, where developers are only a chair slide away.  With more projects spanning</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">code</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tools</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">quality</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tool</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">review</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">collaborator</category>
      <pubDate>Tue, 13 Sep 2011 16:00:30 GMT</pubDate>
      <author>linus.yuen@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/09/13/a-look-into-code-review-tools--code-collaborator</guid>
      <dc:date>2011-09-13T16:00:30Z</dc:date>
      <clearspace:dateToText>4 months, 4 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/a-look-into-code-review-tools--code-collaborator</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1153</wfw:commentRss>
    </item>
    <item>
      <title>Having fun with SWT</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/09/09/having-fun-with-swt</link>
      <description>Background Being new to the SWT I wanted to learn a little about the API by making a simple change to the Commerce Manager UI. I put this post together with the hope that it might have some useful tidbits for other SWT newbies out there. &amp;nbsp; Goal The</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">cmclient</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.2</category>
      <pubDate>Fri, 09 Sep 2011 16:45:15 GMT</pubDate>
      <author>arman.sharif@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/09/09/having-fun-with-swt</guid>
      <dc:date>2011-09-09T16:45:15Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/having-fun-with-swt</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1149</wfw:commentRss>
    </item>
    <item>
      <title>Index Replication With Solr 1.4</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/08/26/index-replication-with-solr-14</link>
      <description>NOTE:   All testing done using EP 6.3.1(solr 1.4).  Any numbers regarding performance should be treated as results of beta testing. &amp;nbsp; Previous to Solr 1.4 (included in EP 6.3), index replication was handled by a cron job.  The job would execute</description>
      <pubDate>Fri, 26 Aug 2011 21:24:40 GMT</pubDate>
      <author>mike.klemarewski@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/08/26/index-replication-with-solr-14</guid>
      <dc:date>2011-08-26T21:24:40Z</dc:date>
      <clearspace:dateToText>5 months, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/index-replication-with-solr-14</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1152</wfw:commentRss>
    </item>
    <item>
      <title>Load tuning - the Kobayashi Maru of OpenJPA</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/08/04/load-tuning--the-kobayashi-maru-of-openjpa</link>
      <description>In Star Trek there is a test named the Kobayashi Maru given to all Starfleet Academy cadets. In this test the civilian vessel Kobayashi Maru is disabled and trapped in the Klingon Neutral Zone, and the cadet must choose whether to leave the ship to</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">openjpa</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">load</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">fetch</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">kobayashi</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maru</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">kirk</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">plan</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tuners</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">large</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">object</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">graph</category>
      <pubDate>Thu, 04 Aug 2011 14:44:24 GMT</pubDate>
      <author>simon.droscher@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/08/04/load-tuning--the-kobayashi-maru-of-openjpa</guid>
      <dc:date>2011-08-04T14:44:24Z</dc:date>
      <clearspace:dateToText>6 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/load-tuning--the-kobayashi-maru-of-openjpa</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1148</wfw:commentRss>
    </item>
    <item>
      <title>A higher-performing CachingStoreResolver</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/07/18/a-higher-performing-cachingstoreresolver</link>
      <description>The performance of the OOTB CachingStoreResolver begins to degrade when more than a handful of stores are configured in EP. This post describes a simple replacement implementation that scales much better. &amp;nbsp; The problem &amp;nbsp; The StoreResolver is</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">storefront</category>
      <pubDate>Tue, 19 Jul 2011 00:11:34 GMT</pubDate>
      <author>david.clark@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/07/18/a-higher-performing-cachingstoreresolver</guid>
      <dc:date>2011-07-19T00:11:34Z</dc:date>
      <clearspace:dateToText>6 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/a-higher-performing-cachingstoreresolver</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1145</wfw:commentRss>
    </item>
    <item>
      <title>The Importance of tearDown() in JUnit 3</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/06/14/the-importance-of-teardown-in-junit-3</link>
      <description>Why is memory never enough? &amp;nbsp; Our customer project has a few dozens of integration JUnit tests.  Those are tests coded as JUnit tests loading the core application Spring context to verify the correct behavior of certain parts of our application.</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <pubDate>Tue, 14 Jun 2011 23:32:07 GMT</pubDate>
      <author>yanko.zhivkov@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/06/14/the-importance-of-teardown-in-junit-3</guid>
      <dc:date>2011-06-14T23:32:07Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/the-importance-of-teardown-in-junit-3</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1141</wfw:commentRss>
    </item>
    <item>
      <title>Setting up EclEmma for Code Coverage</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/06/13/setting-up-eclemma-for-code-coverage</link>
      <description>Introduction &amp;nbsp; EclEmma is a free code coverage tool; it works by determining which  parts of Java code are executed during particular  program launches.  For our purposes, these will likely be JUnit test programs. &amp;nbsp; EclEmma: installs as a</description>
      <pubDate>Mon, 13 Jun 2011 16:46:17 GMT</pubDate>
      <author>andrew.hendriks@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/06/13/setting-up-eclemma-for-code-coverage</guid>
      <dc:date>2011-06-13T16:46:17Z</dc:date>
      <clearspace:dateToText>7 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/setting-up-eclemma-for-code-coverage</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1142</wfw:commentRss>
    </item>
    <item>
      <title>Command line junkie: How to run wars with Tomcat Maven plugin</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/04/27/command-line-junkie-how-to-run-wars-with-tomcat-maven-plugin</link>
      <description>I have a love/hate relationship with Eclipse.  It's a great editor with sane default key mappings, but it tries to be too much.  One thing that never worked all that well is the WTP plugin for managing application servers. How many times have you</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maven</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">build</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tomcat</category>
      <pubDate>Wed, 27 Apr 2011 18:54:25 GMT</pubDate>
      <author>ronald.chen@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/04/27/command-line-junkie-how-to-run-wars-with-tomcat-maven-plugin</guid>
      <dc:date>2011-04-27T18:54:25Z</dc:date>
      <clearspace:dateToText>9 months, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/command-line-junkie-how-to-run-wars-with-tomcat-maven-plugin</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1140</wfw:commentRss>
    </item>
    <item>
      <title>Visualizing OpenJPA Entity Graphs</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/04/04/visualizing-openjpa-entity-graphs</link>
      <description>Overview &amp;nbsp; 'A picture is worth a thousand words' is a really good saying and it proves to be true in many situations. At Elastic Path, we use a tool called OpenJPA Grapher that helps us build a complex graph of entities that are part of the Elastic</description>
      <pubDate>Mon, 04 Apr 2011 18:07:06 GMT</pubDate>
      <author>yanko.zhivkov@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/04/04/visualizing-openjpa-entity-graphs</guid>
      <dc:date>2011-04-04T18:07:06Z</dc:date>
      <clearspace:dateToText>10 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/visualizing-openjpa-entity-graphs</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1137</wfw:commentRss>
    </item>
    <item>
      <title>Using the Maven Reactor plugin when building maven projects in binary based development</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/03/31/using-the-maven-reactor-plugin-when-building-maven-projects-in-binary-based-development</link>
      <description>One of the quirks that I used to have while developing using binary based development is the fact that we have multiple maven projects, and changes to one of the projects (ie. core) will need to be rebuilt in other projects that depend on it (ie.</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">configuration</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maven</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">build</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">binary</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">development</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">based</category>
      <pubDate>Thu, 31 Mar 2011 18:05:43 GMT</pubDate>
      <author>tommy.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/03/31/using-the-maven-reactor-plugin-when-building-maven-projects-in-binary-based-development</guid>
      <dc:date>2011-03-31T18:05:43Z</dc:date>
      <clearspace:dateToText>10 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/using-the-maven-reactor-plugin-when-building-maven-projects-in-binary-based-development</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1136</wfw:commentRss>
    </item>
    <item>
      <title>How-to: Use com.elasticpath.test.application in your Maven project for integration testing</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/03/25/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</link>
      <description>Overview: Elastic Path 6.2.2 comes with a little known project called "com.elasticpath.test.application". This project is used as a connector to enable integration testing by exposing the spring application context to hook up Elastic Path core services</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maven</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.2.2</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">test.application</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">com.elasticpath.test.application</category>
      <pubDate>Fri, 25 Mar 2011 18:33:21 GMT</pubDate>
      <author>tommy.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/03/25/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</guid>
      <dc:date>2011-03-25T18:33:21Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1133</wfw:commentRss>
    </item>
  </channel>
</rss>


