<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-1131270310109486733</atom:id><lastBuildDate>Sat, 07 Nov 2009 17:00:32 +0000</lastBuildDate><title>Thoughts of a Syrup Sucker</title><description /><link>http://syrupsucker.blogspot.com/</link><managingEditor>noreply@blogger.com (Jason Drake)</managingEditor><generator>Blogger</generator><openSearch:totalResults>53</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/ThoughtsOfASyrupSucker" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2941516980918395314</guid><pubDate>Sat, 07 Nov 2009 16:56:00 +0000</pubDate><atom:updated>2009-11-07T09:00:32.644-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">games</category><category domain="http://www.blogger.com/atom/ns#">civilization4</category><title>Civilization 4 on Windows 7</title><atom:summary>If you install and attempt to run Civilization 4 on Windows 7 you will likely receive an error similiar to the following:



I was able to resolve this by downloading and installing the latest released runtime version of DirectX.  I suppose if you install and play many games you likely have a newer version of the DirectX runtime, but this game was my favorite and was the first (and currently only</atom:summary><link>http://syrupsucker.blogspot.com/2009/11/civilization-4-on-windows-7.html</link><author>noreply@blogger.com (Jason Drake)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_rO3pKY6Gt0k/SvWnFjlw5SI/AAAAAAAAAd4/fmBWHMSyjaA/s72-c/civ4error.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-116095133599485120</guid><pubDate>Sat, 06 Jun 2009 21:19:00 +0000</pubDate><atom:updated>2009-06-06T14:21:53.873-07:00</atom:updated><title>Pygments for Source Highlighting</title><atom:summary>I mentioned to a colleague a week ago that I wanted to provide better syntax highlighting of source code in my blog entries.  He suggested I look at Pygments which is a "generic syntax highlighter for general use in all kinds of software such as forum systems, wikis or other applications that need to prettify source code.".  I have to admit, I kind of like it and it is relatively easy to use (</atom:summary><link>http://syrupsucker.blogspot.com/2009/06/pygments-for-source-highlighting.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6887305779236559610</guid><pubDate>Sat, 06 Jun 2009 05:33:00 +0000</pubDate><atom:updated>2009-06-06T14:23:04.299-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><category domain="http://www.blogger.com/atom/ns#">GXT</category><title>GXT 2.0 and Selenium - Part 1</title><atom:summary>For those of you who follow the GXT toolkit know, they are currently in the process or preparing for the release of the 2.0 version.  I converted to the 2.0 M1 version a few weeks ago and other than a few issues, have been able to continue using my application (and building on it).  However when I upgraded to the 2.0 M2 version, I had several key areas that no longer worked.  Of course, while I </atom:summary><link>http://syrupsucker.blogspot.com/2009/06/gxt-20-and-selenium.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6982846800092119621</guid><pubDate>Thu, 28 May 2009 18:28:00 +0000</pubDate><atom:updated>2009-06-06T14:23:17.537-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Selenium</category><category domain="http://www.blogger.com/atom/ns#">GXT</category><title>Selenium with GXT: getting textfields to emit those key events</title><atom:summary>In my Stamp Editor I have a tree browser which can browse collections, albums and countries.  Directly above this, I have a StoreFilterField in which I can type text to filter the tree.  I wanted to write a few selenium tests for this functionality to verify the items are found.  The problem I ran into is when I told selenium to type the text, the text would appear but the filter would not get </atom:summary><link>http://syrupsucker.blogspot.com/2009/05/selenium-with-gxt-getting-textfields-to.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-224860933032522940</guid><pubDate>Fri, 27 Mar 2009 04:30:00 +0000</pubDate><atom:updated>2009-03-26T21:48:41.129-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">JSON</category><category domain="http://www.blogger.com/atom/ns#">JAXB</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">Jersey</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><title>Using JSON with JAXB in new Jersey 1.0.2</title><atom:summary>Jersey 1.0.2 was released in early February and I just got around to updating to it.  I was quite excited to read about the new support for JAXB marshalling to JSON formats (this was introduced I believe in an earlier release but not well detailed).  Jakub Podlesak has some nice articles on this functionality on his blog and would recommend reading them.  One thing I found, is initially I </atom:summary><link>http://syrupsucker.blogspot.com/2009/03/using-json-with-jaxb-in-new-jersey-102.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-8684651413042299269</guid><pubDate>Sat, 14 Mar 2009 21:05:00 +0000</pubDate><atom:updated>2009-03-14T14:09:40.431-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GAE</category><title>Referencing keys of objects in db.Models</title><atom:summary>The Google App Engine revolves around keys.  If you have references to other objects within your Models, it is important to understand the consequence of accessing the model (to prevent fetch statements).  In particular, if you only need to Key of the item (or an attribute on the Key such as the id()) then you want to avoid inflating the persistable.  There are numerous suggestions on how to </atom:summary><link>http://syrupsucker.blogspot.com/2009/03/referencing-keys-of-objects-in-dbmodels.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-812433500388626796</guid><pubDate>Tue, 10 Mar 2009 15:47:00 +0000</pubDate><atom:updated>2009-03-10T12:29:20.575-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GAE</category><category domain="http://www.blogger.com/atom/ns#">GWT</category><title>GWT and Google App Engine - An Update</title><atom:summary>In my previous post GWT and Google App Engine - How to Develop! I outlined an approach one could take to develop a GWT application using the Google App Engine (either from the outset or partially mapping services to GAE over time). In the article I recommended the usage of the HttpRedirectFilter. While this filter worked well using the GAE SDK, I ran into problems connecting to google's remote </atom:summary><link>http://syrupsucker.blogspot.com/2009/03/gwt-and-google-app-engine-update.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-3573059790432085664</guid><pubDate>Sun, 01 Mar 2009 16:45:00 +0000</pubDate><atom:updated>2009-03-01T09:38:27.777-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GAE</category><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><title>GWT and Google App Engine - How to develop!</title><atom:summary>So I have developed an application in GWT using the GXT library which is currently connecting to a Restful WebService through Tomcat and using JPA to access my MySQL Database. I recently had a disk failure on this system, and so have become acutely aware of the possibility at some point I might want to have my application hosted.


I was looking at the Google App Engine, and wanted to experiment </atom:summary><link>http://syrupsucker.blogspot.com/2009/03/gwt-and-google-app-engine-how-to.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-1831019806357600470</guid><pubDate>Wed, 18 Feb 2009 21:48:00 +0000</pubDate><atom:updated>2009-02-18T14:08:17.853-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">MySQL</category><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">HSQLDB</category><category domain="http://www.blogger.com/atom/ns#">JPA</category><title>JPQL and Upper case queries in LIKE</title><atom:summary>I had a situation where I needed to write a query which would perform upper case comparisons in a LIKE statement. It took me a while to figure this out, mainly because I didn't realize the right-side of the LIKE statement does not support any of the functions. So given a query like this:



  SELECT name FROM Countries WHERE name LIKE '%someValue%';



to write this in a valid JPQL format (</atom:summary><link>http://syrupsucker.blogspot.com/2009/02/jpql-and-upper-case-queries-in-like.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-7561278738115066064</guid><pubDate>Sun, 07 Dec 2008 03:03:00 +0000</pubDate><atom:updated>2008-12-06T19:08:09.323-08:00</atom:updated><title>GXT Tree and Loading ... Alternative Design (Validated)</title><atom:summary>In my previous blog I had proposed a design which I could use to dynamically load the tree based on several different modeled objects.  I was successful in implementing this.  One of the tricks was to ensure the stores were loaded prior to building the tree, and to do this, I wrote a handler which would load each of the stores and listen for the completion of the loads and then build the tree </atom:summary><link>http://syrupsucker.blogspot.com/2008/12/gxt-tree-and-loading-alternative-design_06.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-5799880755752928138</guid><pubDate>Sun, 07 Dec 2008 02:52:00 +0000</pubDate><atom:updated>2008-12-06T19:01:32.893-08:00</atom:updated><title>YSlow and Cache-Headers</title><atom:summary>If you run YSLow on one of your web applications, you can obtain some really useful information about improving the performance of your application.  One common performance improvement is to set expiration headers on static resources (such as CSS, JS and image files). Setting this header, will help preserve the file in the browser cache, thus preventing reload of the image on subsequent page </atom:summary><link>http://syrupsucker.blogspot.com/2008/12/yslow-and-cache-headers.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-4244626757805776412</guid><pubDate>Tue, 02 Dec 2008 20:41:00 +0000</pubDate><atom:updated>2008-12-02T13:15:40.736-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">GXT</category><category domain="http://www.blogger.com/atom/ns#">ExtJS</category><title>GXT Tree and Loading ... Alternative Design</title><atom:summary>This is a followup blog to my previous blog entry on GXT Tree and Loading from Restful URLs. While this approach worked, I had concerns over the number of AJAX requests as the tree is fully "expanded". As well, I was considering another possible issue:


The BaseModel objects representing the Country, Album objects are used elsewhere in the client (not just within my tree). 

In this sense, the </atom:summary><link>http://syrupsucker.blogspot.com/2008/12/gxt-tree-and-loading-alternative-design.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6427217027769886061</guid><pubDate>Tue, 02 Dec 2008 03:44:00 +0000</pubDate><atom:updated>2008-12-01T20:37:41.945-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">ExtJS</category><title>GXT Tree and Loading with REST</title><atom:summary>Anyone who has used GXT can tell you that it is very powerful, but examples (and the javadoc) are still few and hard to find.  The examples that come with the SDK are great (see Ext GWT 1.2 Samples), but if you need to something beyond these you typically need to figure it out on your own.  I hope to be able to write a series of blog articles on some of the designs I have figured out for the </atom:summary><link>http://syrupsucker.blogspot.com/2008/12/gxt-tree-and-loading-with-rest.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-4351125129745295233</guid><pubDate>Sat, 04 Oct 2008 06:11:00 +0000</pubDate><atom:updated>2008-10-03T23:19:18.325-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">ExtJS</category><title>ExtJS Action.submit response</title><atom:summary>When an ExtJS form is submitted, the successful completion of the asynchronous call will call the function mapped to the success config value.  This function will take two parameters form and action.  If you are returning JSON from the call you an access this directly from the action parameter.





  var _form = // ... get your form (eg. formPanel.form)
  _form.submit({ scope.this, waitMsg:'</atom:summary><link>http://syrupsucker.blogspot.com/2008/10/extjs-actionsubmit-response.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6065383483035473859</guid><pubDate>Sat, 04 Oct 2008 03:31:00 +0000</pubDate><atom:updated>2008-10-03T20:43:29.216-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">JAXB</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><title>Collections and JAX-RS</title><atom:summary>As I had previously reported, both RestEasy and Jersey both suffered from the inability to return a collection of JAXB marshalled objects.  I was thinking on this a little, and while I could use the JAXBCollection fix in Jersey, it seemed a little bit of a hack until it goes into the 1.0 release.  Instead (for now), I have written a few wrapper classes which they themselves are XmlRootElements </atom:summary><link>http://syrupsucker.blogspot.com/2008/10/collections-and-jax-rs.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2358491800313589256</guid><pubDate>Fri, 03 Oct 2008 21:14:00 +0000</pubDate><atom:updated>2008-10-03T14:47:03.169-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Servlet</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><title>Deploying RestEasy in Tomcat 6.0</title><atom:summary>Since I was successful deploying Jersey to Tomcat 6.0, I decided to check out RestEasy from JBoss.  One issue I ran into with Jersey was it's inability to XML serialize a collection of objects.  This is bug ID is 18, and it is fixed for the 1.0 release (however a beta of this does not appear to be available yet), but I decided to see if RestEasy (a non-reference implementation) has the same issue</atom:summary><link>http://syrupsucker.blogspot.com/2008/10/deploying-resteasy-in-tomcat-60.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-9209720705100368748</guid><pubDate>Fri, 03 Oct 2008 02:39:00 +0000</pubDate><atom:updated>2008-10-02T20:07:21.735-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Servlet</category><category domain="http://www.blogger.com/atom/ns#">REST</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><title>Deploying Jersey in Tomcat 6.0</title><atom:summary>Jersey is a reference implementation for the JAX-RS (JSR-311) for building RESTful Web services.  It is nearing approval with the JSR committees.  While there are many wikis and articles in using Jersey with Netbeans (downloading the Netbeans 6.1 EE package includes everything you need for JSR-311), there was very little information on using Tomcat 6.0 with Jersey.  After piecing together several</atom:summary><link>http://syrupsucker.blogspot.com/2008/10/deploying-jersey-in-tomcat-60.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-8348187042045008617</guid><pubDate>Thu, 02 Oct 2008 16:40:00 +0000</pubDate><atom:updated>2008-10-02T12:48:06.076-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Servlet</category><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">Java</category><category domain="http://www.blogger.com/atom/ns#">REST</category><title>Making your servlet application URLs more Restful</title><atom:summary>If you are a developer who likes to work with Java you may have come to know REST and Restful Web Services.  The real advantage of REST is its ability to get rid of some of the "webspeak" and make your URLs a little more platform independent.  As a client developer it is much nicer to make a request to http://somehost/Application/stamp/5533 to retrieve stamp 5533 than the traditional http://</atom:summary><link>http://syrupsucker.blogspot.com/2008/10/making-your-servlet-application-urls.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-160090545230900223</guid><pubDate>Tue, 30 Sep 2008 03:12:00 +0000</pubDate><atom:updated>2008-09-29T20:17:39.579-07:00</atom:updated><title>Remote Assistance - Not always able to connect</title><atom:summary>I ran into a situation where I could not connect to my fathers PC using Remote Assistance.  Now, given that he lives about 3000 miles away it is essential that I am able to connect with Remote Assistance to help him with miscellanious activities.  I discovered that the Remote Assistance files are really nothing more than XML, and upon edting the XML I realized there was a series of invalid IPs in</atom:summary><link>http://syrupsucker.blogspot.com/2008/09/remote-assistance-not-always-able-to.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-7771282929516306224</guid><pubDate>Tue, 30 Sep 2008 02:58:00 +0000</pubDate><atom:updated>2008-09-29T20:11:18.657-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">ExtJS</category><title>ExtJS ComboBox - Act like HTML Select</title><atom:summary>At first I struggled to get my ExtJS ComboBoxes to act like a straight HTML Select.  In my application, I have a grid which loads the data into a store via AJAX.  Later, create or edit dialogs display which contain a combobox of items represented by the store.  Rather than load these again from the server, I wanted to reuse the data from the store.  The problem I had is selecting a value in the </atom:summary><link>http://syrupsucker.blogspot.com/2008/09/extjs-combobox-act-like-html-select.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-8561957433450500713</guid><pubDate>Tue, 26 Aug 2008 15:30:00 +0000</pubDate><atom:updated>2008-09-12T09:32:52.123-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">Toplink</category><category domain="http://www.blogger.com/atom/ns#">JPA</category><title>JPA and Optional Associations</title><atom:summary>I was writing some unit tests to test a few of my queries and noticed they were failing to return results (even though the resultant rows were clearly in the database). Looking into my changes, the only differences was that I recently added the EclipseLink eclipselink.join-fetch for two one-to-many relationships. From looking at the resultant SQL, it became clear what the problem was. By adding </atom:summary><link>http://syrupsucker.blogspot.com/2008/08/jpa-and-optional-associations.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2276611574976578571</guid><pubDate>Fri, 22 Aug 2008 21:14:00 +0000</pubDate><atom:updated>2008-08-23T09:52:30.977-07:00</atom:updated><title>Refactoring Followup - Strange Side Effect</title><atom:summary>While I was quick to point out that my refactoring of my services end up being a little bit painful on the Swing Heavy-client side, when it came time to refactor my web-services client (currently a series of dedicated servlets used by my mobile devices) it was surprisingly a clean update.  Why was this?  What lesson can I pull from this.  The main one was that the web-services code was very </atom:summary><link>http://syrupsucker.blogspot.com/2008/08/refactoring-followup-strange-side.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-4272640131424331099</guid><pubDate>Fri, 15 Aug 2008 17:48:00 +0000</pubDate><atom:updated>2008-08-15T11:00:59.956-07:00</atom:updated><title>Refactoring: Biting off more than you can chew?</title><atom:summary>So as most can assert from reading my blog I have developed a stamp tracking software "suite" of tools.  The core of this was based off a JPA implementation which was recently moved to EclipseLink.  With some of the new tools available to Eclipse for use with JPA (in particular Dali), I decided to think about reorganizing my services and trying to streamline some of my code (Using </atom:summary><link>http://syrupsucker.blogspot.com/2008/08/refactoring-biting-off-more-than-you.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-105829015611258821</guid><pubDate>Tue, 05 Aug 2008 18:31:00 +0000</pubDate><atom:updated>2008-08-05T11:51:43.106-07:00</atom:updated><title>Certifications even for the experienced?</title><atom:summary>Those of you who know me know that I sometimes shun the world of academia. Not that I do not think education is useful. I do. I am the current holder of two bachelor degrees and numerous certifications and I can honestly say they have proven useful in my career. But too often I see a candidate interviewing at my company who has years of academic training (multiple bachelor degrees, masters </atom:summary><link>http://syrupsucker.blogspot.com/2008/08/certifications-even-for-experienced.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-7876884023546605584</guid><pubDate>Mon, 28 Jul 2008 02:42:00 +0000</pubDate><atom:updated>2008-07-27T20:08:54.293-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">UnitTest</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><category domain="http://www.blogger.com/atom/ns#">JPA</category><title>Automatically recording Create/Update Timestamps with JPA</title><atom:summary>Now that I am using Bugzilla to track various bugs and enhancements for my projects, I finally got around to addressing this issue of "Provide the ability to record the create/update timestamp." for my stamp objects.  This seems simple enough, and most database applications record this information, however by default this is not something that is automated by the JPA frameworks (unlike the </atom:summary><link>http://syrupsucker.blogspot.com/2008/07/automatically-recording-createupdate.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></item></channel></rss>
