<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-1131270310109486733</atom:id><lastBuildDate>Wed, 25 Feb 2026 17:26:49 +0000</lastBuildDate><category>JPA</category><category>Eclipse</category><category>EclipseLink</category><category>GWT</category><category>Java</category><category>GXT</category><category>Selenium</category><category>Toplink</category><category>HSQLDB</category><category>JAX-RS</category><category>REST</category><category>JAXB</category><category>UnitTest</category><category>ExtJS</category><category>JSON</category><category>C#</category><category>GAE</category><category>Servlet</category><category>Smartphone</category><category>Arquillian</category><category>MySQL</category><category>NodeJS</category><category>AngularJS</category><category>Baby</category><category>ChosenJS</category><category>GS4</category><category>Glassfish</category><category>Jersey</category><category>MOXy</category><category>Usability</category><category>WMP</category><category>civilization4</category><category>foreui</category><category>games</category><category>prototyping</category><title>Thoughts of a Syrup Sucker</title><description></description><link>http://syrupsucker.blogspot.com/</link><managingEditor>noreply@blogger.com (Jason Drake)</managingEditor><generator>Blogger</generator><openSearch:totalResults>71</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-3150554448123216069</guid><pubDate>Wed, 30 Dec 2015 06:25:00 +0000</pubDate><atom:updated>2015-12-29T22:25:55.113-08:00</atom:updated><title>NodeJS and Promises with MySQL Connector - beware of the unreleased connection</title><atom:summary type="text">In my NodeJS application I am using the nice MySQL library node-MySQL.  I have heavily used Q promises for managing the asynchronous nature of code vs. using callbacks.  By using a connection pool, I can reuse connections without having to worry about re-negotiating with the database with every query.  My general design is to get a connection from the pool, do whatever I need to do with it and </atom:summary><link>http://syrupsucker.blogspot.com/2015/12/nodejs-and-promises-with-mysql.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-1748805206576672100</guid><pubDate>Sun, 20 Dec 2015 04:25:00 +0000</pubDate><atom:updated>2015-12-19T20:25:13.438-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">NodeJS</category><title></title><atom:summary type="text">Recently I had to reinstall my operating system and chose Windows 10.  I had an issue with my NodeJS 3.x environment and switched to NodeJS 5.x.  In doing so, I had issues with the node-gyp again.

It is not clear the order in which I installed everything or if the order matters, but I had to install both the &quot;Visual Studio 2015 Community Edition&quot; as well as the &quot;Visual Studio C++ Build Tools&quot;.  </atom:summary><link>http://syrupsucker.blogspot.com/2015/12/recently-i-had-to-reinstall-my.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6963688235496701602</guid><pubDate>Sat, 03 Oct 2015 14:15:00 +0000</pubDate><atom:updated>2015-12-29T22:25:38.229-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">NodeJS</category><title>Installing libraries with node-gyp and NodeJS 4.1+ on Windows 8+</title><atom:summary type="text">I have noticed that some node modules come down and compile on Windows.  These may be because they detect a compiler environment or because as part of their install they need to be compiled with native libraries.  Either way, inevitably you may run into node-gyp trying to compile.  Assuming you have the correct tool chain (see the [node-gyp github site](https://github.com/nodejs/node-gyp)) you </atom:summary><link>http://syrupsucker.blogspot.com/2015/10/installing-libraries-with-node-gyp-and.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2832726230174297753</guid><pubDate>Mon, 20 Oct 2014 15:02:00 +0000</pubDate><atom:updated>2014-10-20T08:02:26.773-07:00</atom:updated><title>Webstorm supports Open Source projects</title><atom:summary type="text">Since all of my open source projects are turning to HTML-5/JS based architectures, I started looking into platforms to develop stamp-webservices 4.0 that would be on the NodeJS platform.  I am also supporting ng-scrolling-table which is AngularJS based.  I had previously used Netbeans 8.0.X for developing ng-scrolling-table, however the lack of NodeJS debugging and support for many of the NodeJS </atom:summary><link>http://syrupsucker.blogspot.com/2014/10/webstorm-supports-open-source-projects.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-3954473958770221507</guid><pubDate>Thu, 28 Aug 2014 02:36:00 +0000</pubDate><atom:updated>2014-08-27T19:36:59.608-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">WMP</category><title>Playing flac files in Windows Media Player (WMP)</title><atom:summary type="text">If you are like me, you don&#39;t have a lot of tools for playing video and music files.  You use a few simple tools and keep in simple.  In my case I primarily use WMP (Windows Media Player) on Windows 8.X and sometimes VLC Player, (esp. on my Linux systems).

If you try and play .flac files in WMP they will not play because the codec is not available.  No worries, as there is a great project I </atom:summary><link>http://syrupsucker.blogspot.com/2014/08/playing-flac-files-in-wmp-windows-media.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-6529846089059935670</guid><pubDate>Sat, 12 Oct 2013 21:32:00 +0000</pubDate><atom:updated>2013-10-12T14:32:29.778-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Selenium</category><category domain="http://www.blogger.com/atom/ns#">UnitTest</category><title>Writing Selenium Tests in a more DSL like way</title><atom:summary type="text">I noted in a previous blog post that I was starting to write more tests in a more fluent DSL like manner.  I thought I would illustrate this.  Here is an example of a test that does the following (assuming you are logged in on the home screen):

From the navigator (think of it as a button bar) click the &quot;Create wantlist&quot; - this will launch a create wantlist editor and return this solvent.
We want</atom:summary><link>http://syrupsucker.blogspot.com/2013/10/writing-selenium-tests-in-more-dsl-like.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-9084410911360696421</guid><pubDate>Sat, 12 Oct 2013 21:17:00 +0000</pubDate><atom:updated>2013-10-12T14:17:06.850-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">AngularJS</category><category domain="http://www.blogger.com/atom/ns#">ChosenJS</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><title>Selecting ChosenJS values with Selenium</title><atom:summary type="text">I had previously blogged about selection of GXT selections with selenium and figured it might be worthwhile if I posted what I was doing with my new AngularJS app that is using ChosenJS as my selection of choice (I wrapped this in a simple directive)

For my selenium tests, I try and write most of the code in DSL format in a object termed a Solvent.&amp;nbsp; We use this term at my place of </atom:summary><link>http://syrupsucker.blogspot.com/2013/10/selecting-chosenjs-values-with-selenium.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-5060598983092295611</guid><pubDate>Fri, 04 Oct 2013 04:48:00 +0000</pubDate><atom:updated>2013-10-03T21:48:08.962-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Arquillian</category><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">Glassfish</category><category domain="http://www.blogger.com/atom/ns#">GS4</category><title>Arquillian with Glassfish 4 - early trials</title><atom:summary type="text">With the release of Glassfish 4 and J2EE version 7, I decided to work at upgrading my stamp web services application to the platform.  An important part of my project is my 580 odd tests that include approximately 300 or so Arquillian tests.  Since my application takes advantage of Container Managed transaction context and persistence providers, it is not sufficient for me to simply tests these </atom:summary><link>http://syrupsucker.blogspot.com/2013/10/arquillian-with-glassfish-4-early-trials.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2106517895805058092</guid><pubDate>Fri, 09 Nov 2012 16:39:00 +0000</pubDate><atom:updated>2012-11-09T11:46:12.938-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><category domain="http://www.blogger.com/atom/ns#">JSON</category><category domain="http://www.blogger.com/atom/ns#">MOXy</category><title>J2EE Application with MOXy</title><atom:summary type="text">As part of my refactoring of my existing J2EE application using JAX-RS, I wanted to try and reduce the JAXB custom code in place.  Previously I was using Jackson and Jersey for JSON serialization using the &quot;Mapped&quot; notation.  This involved creating my own JAXBContext object and I was required to create some special mapping processing so that I could map an attribute as etiher an array, non-string</atom:summary><link>http://syrupsucker.blogspot.com/2012/11/j2ee-application-with-moxy.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-8074945124424861843</guid><pubDate>Fri, 09 Nov 2012 15:46:00 +0000</pubDate><atom:updated>2012-11-09T07:47:23.277-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Arquillian</category><category domain="http://www.blogger.com/atom/ns#">Eclipse</category><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><title>EclipseLink logging with Arquillian in Eclipse</title><atom:summary type="text">I have been doing some experimentation with Arquillian for testing my refactored J2EE application in embedded glassfish.  I really like it so far, but I ran into an issue where me test-persistence.xml file use did not see to provide anything more than SERVERE level logging from eclipselink.  I had tried setting the property 
&amp;lt;property name=&amp;quot;eclipselink.logging.logger&amp;quot; value=&amp;quot;</atom:summary><link>http://syrupsucker.blogspot.com/2012/11/eclipselink-logging-with-arquillian-in.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-4023986547239986371</guid><pubDate>Thu, 01 Nov 2012 22:39:00 +0000</pubDate><atom:updated>2012-11-01T15:40:17.486-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">JAX-RS</category><category domain="http://www.blogger.com/atom/ns#">JAXB</category><category domain="http://www.blogger.com/atom/ns#">JPA</category><title>Diving into J2EE6 with JTA</title><atom:summary type="text">I have been silent for a long time on the blog (I have been busy - never fear) but simply have not spent the time here to document my activities.
I was in the process of doing a major overhaul on my server-side JAX-RS WEB Services and their accompanying persistence services to bring things up to a little more standard approach.  In particular my goals were to:
Utilize more dependency injection (</atom:summary><link>http://syrupsucker.blogspot.com/2012/11/diving-into-j2ee6-with-jta.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2644221293815861746</guid><pubDate>Fri, 16 Jul 2010 02:28:00 +0000</pubDate><atom:updated>2010-07-15T19:51:23.334-07:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GXT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><category domain="http://www.blogger.com/atom/ns#">UnitTest</category><title>Firefox, Selenium GXT and the nasty Quick Find Links Only</title><atom:summary type="text">So I have seen this intermittent error with my selenium tests that drives me up the wall. I&#39;ll be running a test and all of a sudden a little &quot;Quick Find&quot; box shows up in the lower left corner in Firefox (not the same as CTRL-F). This appears to be some sort of &quot;old feature&quot; of firefox that is used to quickly find links or something in the page (people have complained about it since Firefox 1.0).</atom:summary><link>http://syrupsucker.blogspot.com/2010/07/firefox-selenium-gxt-and-nasty-quick.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-4369096436342114068</guid><pubDate>Sat, 06 Mar 2010 04:30:00 +0000</pubDate><atom:updated>2010-03-05T20:54:56.011-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GXT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><category domain="http://www.blogger.com/atom/ns#">UnitTest</category><title>GXT and Selenium - Part 2</title><atom:summary type="text">First off, to all those who have patiently asked for my solution of GXT combo boxes and selenium, I do apologize for the long time in coming.  While reading my articles is certainly not like being left with a cliff hanger in a movie sequel, I know the pain in waiting anxiously for a solution.

Combo Boxes

After trying many different ways to get combo boxes to work, I have worked out a pattern </atom:summary><link>http://syrupsucker.blogspot.com/2010/03/gxt-and-selenium-part-2.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-5307560772460536245</guid><pubDate>Fri, 19 Feb 2010 04:24:00 +0000</pubDate><atom:updated>2010-02-18T22:50:16.635-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">foreui</category><category domain="http://www.blogger.com/atom/ns#">prototyping</category><title>Reviewing ForeUI to prototype screens</title><atom:summary type="text">Recently I have had the pleasure of working together with one of my coworkers on my Stamp Web Editor project (on our personal time of course). Like all skilled professionals she wanted a chance to try and use some new technologies and libraries (like GXT, JPA and Restful Web Services) and I realized I simply could not continue to develop my hobby application without involving more developers. One</atom:summary><link>http://syrupsucker.blogspot.com/2010/02/reviewing-foreui-to-prototype-screens.html</link><author>noreply@blogger.com (Jason Drake)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6HQgYQQc4EahftrmzAYHBXhCCZRwnp_ToA9xruLW1BpTdBL3pmfhyphenhyphentE494oUPULu6G76UXZ-VTQhDWFoi9LQ9BEEqFzo5HFu17rCQjSA79FJYJ8ZBojZ1pBrtZYDOJNR6AFfMRdrxYQY/s72-c/foreui_update.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2132619417222121541</guid><pubDate>Mon, 25 Jan 2010 17:09:00 +0000</pubDate><atom:updated>2010-01-25T09:33:05.701-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GXT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><title>Selenium and GXT CheckboxListView</title><atom:summary type="text">I recently updated my application to use a menu hooked up to a button in which I display a GXT CheckboxListView of stamp issues.  The general idea is that when defining my stamp if there are flaws (I tend to avoid collecting these) I can check-off the flaws in a drop-down like list.  I added some selenium tests to capture the correct functionality, and came a across a few interesting points I </atom:summary><link>http://syrupsucker.blogspot.com/2010/01/selenium-and-gxt-checkboxlistview.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-8774703512070945051</guid><pubDate>Mon, 18 Jan 2010 05:01:00 +0000</pubDate><atom:updated>2010-01-17T21:10:52.519-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">EclipseLink</category><category domain="http://www.blogger.com/atom/ns#">JPA</category><title>Unable to deploy JPA to Tomcat (Linux server)</title><atom:summary type="text">I had to reimage my linux server due to a catastrophic disk failure.  In doing so, I had to reinstall tomcat(s) (I use two... one for running my stamp app and the stamp test app (selenium testing) and one for running hudson builds).  When my ant script for my stamp application deployed to the &quot;production&quot; tomcat, the start target would fail.  I looked in the tomcat logs and saw this:



Exception</atom:summary><link>http://syrupsucker.blogspot.com/2010/01/unable-to-deploy-jpa-to-tomcat-linux.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-186892524401799552</guid><pubDate>Sun, 13 Dec 2009 17:57:00 +0000</pubDate><atom:updated>2009-12-13T10:06:44.142-08:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GWT</category><category domain="http://www.blogger.com/atom/ns#">GXT</category><title>Upgrading to GWT 2.0 with GXT 2.1.0</title><atom:summary type="text">I had to upgrade my GWT version to 2.0.0 with GXT 2.1.0.  For the most part this was pretty straight forward.  One change that impacted me was the usage of ImageBundle being deprecated.  To convert it to the GWT version of doing things I had to do the following:
extend com.google.gwt.resources.client.ClientBundle instead of ImageBundle
replace @Resource with @Source (from ClientBundle)
the return</atom:summary><link>http://syrupsucker.blogspot.com/2009/12/upgrading-to-gwt-20-with-gxt-210.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-1131270310109486733.post-2170463250601414786</guid><pubDate>Sat, 12 Dec 2009 05:50:00 +0000</pubDate><atom:updated>2009-12-13T10:05:40.737-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#">Selenium</category><title>GXT 2.1.0 Conversion</title><atom:summary type="text">The following is a list of the issues I ran into when I converted from GXT 2.0.1 to GXT 2.1.0.  This is not the complete exhaustive list, however these may provide others with some of the workarounds.


My dialogs will cascade events to the form panels and their contents on the dialog.  A change was made to Layout which requires all components which are receiving the event to have a layoutData </atom:summary><link>http://syrupsucker.blogspot.com/2009/12/gxt-210-conversion.html</link><author>noreply@blogger.com (Jason Drake)</author><thr:total>0</thr:total></item><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#">civilization4</category><category domain="http://www.blogger.com/atom/ns#">games</category><title>Civilization 4 on Windows 7</title><atom:summary type="text">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="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6VCDCXDMg8DzXo5rjN6O1RzmkYlJbtBfy-mhiFsEJHegLxFTPeLgwHIbP8438ubYBbMcYDUFm0S-hxKzY8hP2uOO8Fwcge_1ek2U1BSE1g7UtRzW08XfN7vDhhGv1A2U1-bfkc3byMDI/s72-c/civ4error.png" height="72" width="72"/><thr:total>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 type="text">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 &quot;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.&quot;.  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>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#">GXT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><title>GXT 2.0 and Selenium - Part 1</title><atom:summary type="text">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>3</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#">GXT</category><category domain="http://www.blogger.com/atom/ns#">Selenium</category><title>Selenium with GXT: getting textfields to emit those key events</title><atom:summary type="text">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>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#">JAX-RS</category><category domain="http://www.blogger.com/atom/ns#">JAXB</category><category domain="http://www.blogger.com/atom/ns#">Jersey</category><category domain="http://www.blogger.com/atom/ns#">JSON</category><category domain="http://www.blogger.com/atom/ns#">REST</category><title>Using JSON with JAXB in new Jersey 1.0.2</title><atom:summary type="text">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>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 type="text">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>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 type="text">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&#39;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>0</thr:total></item></channel></rss>