Blogging Roller

Latest links from my Twitter, Google Reader and Flickr accounts.

Shared: iPhone User? 90% Chance You?re On The Latest OS. Android User? 0.4% Chance - Mon Jan 17 22:00:13 EST 2011

snoopdave: RT @BrianR: Colbert drops The Word on Wake County Schools, DISINTEGRATION [video] http://t.co/6mjZn4e” #fb - 2011-01-19 08:46:08.0

snoopdave: I checked in at The Rockford (320 Glenwood Ave) on #Yelp http://bit.ly/g7c6wL - 2011-01-19 18:30:13.0

snoopdave: SonaType survey says "lack of integration" is the biggest complaint about software dev infrastructure #oslc http://bit.ly/dHgyPP - 2011-01-20 08:30:02.0

snoopdave: Just blogged my experiences making Roller 5 work on JBoss 6 http://bit.ly/hSxH7q #fb - 2011-01-20 18:01:27.0

snoopdave: Jarvis says FB and Google war is about mobile, not social http://bit.ly/gwIdqn - 2011-01-21 08:36:01.0

snoopdave: Amazingly detailed map of the world built from Facebook relationship lines #fb http://bit.ly/f1iqfm - 2011-01-21 09:08:05.0

In my quest to make Roller work on Java EE 6, the next server that I tackled was JBoss 6. In this blog I'll describe how I approached the problem what I learned along the way.

Tested with Hibernate JPA

Roller uses JPA for database storage and specifically the Apache OpenJPA implementation. I knew that JBoss uses the Hibernate JPA implementation and I suspected that there would be JPA portability problems, so I decided to run Roller's JUnit tests against Hibernate JPA. There were many test failures and fortunately, the failures were easy to fix.

Latest articles shared via Google Reader:

Latest links shared via Twitter

In my quest to make Roller work on Java EE 6, the first server that I decided to tackle was Glassfish 3. In this blog I'll describe how I approached the problem and what I learned along the way.

Tested with EclipseLink JPA

Roller uses JPA for persistence and specifically the Apache OpenJPA implementation. I knew that GlassFish uses the EclipseLink JPA implementation and I suspected that there would be JPA portability problems, so I decided to run Roller's JUnit tests against EclipseLink JPA. I wanted to find and fix those problems before even touching GlassFish. The tests ran and there were many JPA related failures and errors, most due to differences in the way that EclipseLink handles bi-directional relationships and the use of unmanaged objects.

Latest links from my Twitter, Google Reader and Flickr accounts.

snoopdave: starting to write up my Java EE 6 experiences w/Roller 5 http://bit.ly/fnHBVu - 2011-01-05 15:26:03.0

Shared: Open Source Is The New Shareware - Thu Jan 06 07:00:14 EST 2011

snoopdave posted a photo:

Works very nicely, at least for the short tests I have tried.
2011-01-07 13:30:48.0

Shared: Roller 5 on multiple Java EE AppServers - Fri Jan 07 17:02:13 EST 2011

snoopdave: Interesting comments on "Is JCR Dead?" http://t.co/c8bhmuX via @cmswire - 2011-01-08 12:57:43.0

snoopdave: off to see True Grit... hope we'll like it as much as my bro did http://bit.ly/fNUeic #fb - 2011-01-08 13:32:48.0

snoopdave: Finally, a Rubik's cube that I can solve! http://bit.ly/dJWCQw - 2011-01-08 16:44:56.0

snoopdave: Just ordered a Nexus S to replace my old, slow, call-dropping iPhone 3G http://www.google.com/nexus #fb - 2011-01-09 09:33:08.0

It's hard to believe, but I've been dorking around with Roller, the blog software that powers this site, for almost 10 years now. I started in summer 2001. In the past couple of years, I've had a lot less time to work on Roller. I devoted some of that time to mentoring student developers, which was fun and rewarding. I also spent time making Roller more consumable for developers by making it easier to build, run and deploy to modern Java app servers, which was not really fun but was definitely educational, bloggable even.

Latest links from my Twitter, Google Reader and Flickr accounts.

Shared: Glacier, Yellowstone, and the Grand Tetons Again (2010) - Sun Jan 02 18:19:43 EST 2011

snoopdave: "Nobody wants an app for each content source" http://bit.ly/ijgACO - 2011-01-02 12:10:00.0

snoopdave: RT @sspeiche: Contributed #oslc service provider JUnit-based test suite http://tinyurl.com/2bdasvg more updates coming in the new year - 2011-01-04 08:20:34.0

snoopdave: No coffee and email is down - not a great way to start the work-year http://dilbert.com/strips/comic/2006-10-18/ - 2011-01-04 08:29:39.0

snoopdave: RT @apache_roller: Apache Roller 5.0 RC3 files are available for testing http://rollerweblogger.org/roller/entry/apache_roller_5_0_rc3 - 2011-01-04 08:33:41.0

On the last day of 2010, I made available the third release candidate for Apache Roller 5.0. The main difference between this new candidate and the previous one is that the new RC3 runs on Java EE 6 servers: Glassfish 3, JBoss 6 and Websphere 8 (currently in beta). Making this happen took a lot more work than I expected and I'll blog about that over the next couple of weeks as it is an interesting case study in Java EE 6 portability.

Here's the announcement:

Apache Roller 5.0 Release Candidate RC3 is now available for testing.
Note that this is NOT a release of the Apache Software Foundation or
anybody else; this release candidate is for testing purposes only and
not recommended for production.

   What's new in Roller 5.0:
   https://cwiki.apache.org/confluence/display/ROLLER/What's+new+in+Roller+5.0

   Change list (issues resolved since 4.0)
   http://bit.ly/gAhDWR

   Issues resolved since last release candidate (RC3)
   http://bit.ly/dZ27Nx

   Signed binary and source files. Also, documentation in PDF form
   http://people.apache.org/~snoopdave/apache-roller-5.0/

The biggest change in RC3 is the new support for Java EE 6 application
servers: Glassfish 3, JBoss 6 and Websphere 8 (beta). I've been able
to verify that Roller runs on all of those servers, and I updated the
installation guide to explain in detail how you install on Glassfish,
JBoss and WebSphere.

If you would like to help out then please test RC3, discuss the
problems you encounter here and file specific bugs with steps to
reproduce in the Roller JIRA bug tracking system.

Thanks,
Dave