
Yesterday was the 2nd NLGUG (Dutch Groovy and Grails User Group) meetup in Baarn (close to Amsterdam).
As I live in the south of The Netherlands (close to Maastricht) attenting the meetup meant a 2-hour drive home. So at 00.10 I arrived home, tired, but it was worth it!
The meetup was organized by Erik Pragt and was hold at the VX Company headquarters. We really need to meetup up at Valid's new V-Tower at Eindhoven Flight Forum one day! Perhaps somewhere in October or November when we are settled in.
I must admit that I was not really attracted by the subject: iWebKit
But Sebastien Blanc's workshop turned out to be really fun and impressive!
After a short presentation we did a workshop by building our own Twitter client for the iPhone. And guess what it even worked and looked nice on my Android phone. Now iWebKit only need to support native Android look and feel (feature request?).
We used the Grails iWebKit Plugin (developed by Sebastien himself) and the Twitter Plugin and it's so impressive and cool to see that with a couple lines of code you can build a Twitter client for your mobile. Sebastien promised to put the workshop online so the rest of the world can try it to.
I guess there were around 15 attendees and it's really great to see how enthousiastic they are. Grails also lives in The Netherlands! Hope next time there will be even more people. Check out some photo's of the meetup.
Thursday, July 9, 2009
2nd NLGUG Meetup
Tuesday, July 7, 2009
Grails Google Analytics Plugin

As Marc Palmer already mentioned it's important for the community to download and test Grails 1.2-M1.
I've already started with 1.2-SNAPSHOT builds for my home project but also decided to write a simple Google Analytics plugin and test the plugin development parts of Grails 1.2-M1. Again, it is a very simple plugin but found no blocking issues so far.
About the plugin: It includes a simple tag to embed the Google Analytics tracking code in your views/layouts. Just add <ga:trackPageview /> just before your closing </body> tag and add your Web Property ID to Config.groovy:
// grails google analytics plugin configuration
google.analytics.webPropertyID = "UA-xxxxxx-x"
By default only running your Grails application in production mode the Google Analytics tracking code will be outputted. This makes sense as you don't want to mix development or testing page hits with the ones from production. However if you need you can explicitly enable/disable Google Analytics or use different Web Property ID's per environment. See http://www.grails.org/plugin/google-analytics for details.
Posted by
Marcel Overdijk
at
6:19 AM
0
comments
Labels: Google Analytics, Grails
Wednesday, June 17, 2009
Tweeting now

I believe I created a Twitter account somewhere last year but never used it. But from now on I will try tweeting on a regular basis. You can follow me on http://twitter.com/marceloverdijk.
Screenshot from groovytweets.org
Posted by
Marcel Overdijk
at
2:08 PM
0
comments
Labels: Twitter
Sunday, June 14, 2009
Google App Engine Datastore doubts

I have been looking into Google App Engine since the beginning. I played a little bit with it using Python and Django but never did some serious work. As GAE/J was released back in April I decided to have a serious look by building a real application.
I mean the GAE promise is everything I need: easy to build, easy to maintain, easy to scale and I can run it on Google's infrastructure. And when my application won't be the next Twitter, most likely it will cost me nothing to host it as Google offers enough free quotas for medium and small application. I should also mention that now Grails also runs on GAE (using the App Engine plugin) my life couldn't get easier, but...
The only thing GAE does not offer is a relational datastore. GAE's Datastore, based on BigTable, is a hierarchical, schema-less, non-relational datastore.
One of the nice things relational databases support are the aggregate functions like count, sum, avg etc. If you are using GAE you must "Shift processing from reads to writes" as mentioned in The Softer Side Of Schemas - Mapping Java Persistence Standards To the Google App Engine Datastore presented at Google I/O. In practice this means that when inserting or updating a record you must calculate and store the count, sum, avg, etc. values of the whole table. But what if you have many conditional groupings? Let's take an example:
@Entity
class Person {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
String id;
String name;
//Date birthdate;
Integer age;
String address;
String city;
String postalCode;
}
Now imagine I want to be able to (1) get the total number of persons and (2) the average age. Everytime I would create, update or delete a person I should calculate both and store them. Not a big deal, but in my opinion already to much hassle.
But then I also want these values per city... So for each city I should store these values. Next I want them also per postalCode or a specific range of the postalCode. You see where I'm going to? Every create, update or delete of a person would result in a lot of caluculation and storing values.
And then worse, my agile product owner comes in and want to add a boolean indicating a person is a male or not. And guess what, number of persons and average age should additionally be calculated also for this male/female indicator, and to make it worse also in combination with city and postalCode...
I truly believe GAE's Datastore is suitable for many applications don't needing features part of most relational databases. But if you need aggregate queries or common SQL functions (both most likely needed when you are trying to get some analytical data) you should really think twice.
I hope one day GAE's current Datastore will support aggregate functions or additionally a relational datastore will be provided. Then I think GAE would be my preferred Cloud platform.
Posted by
Marcel Overdijk
at
4:24 AM
20
comments
Labels: GAE, Google, Google App Engine
Monday, June 8, 2009
Microsoft finally seeing the light ;-)
Microsoft is finally seeing the light!! Watch the video below to see Ted Neward demonstrate the new JDBC 4 driver for Microsoft SQL Server at the Microsoft booth at JavaOne.
Funny thing is Ted is using Grails and also a MacBook.
Posted by
Marcel Overdijk
at
11:44 PM
1 comments
Which hosting party to choose?

For some personal project I'm currently looking for a hosting party.
I started very open minded to use whatever technology to build the web application from Grails, Spring Roo, Ruby on Rails to CakePHP or even Drupal.
I don't have that many requirements:
- Hosting party should be a respected company
- Ability to scale out easily
- Offer Subversion service to manage my application sources
- And (very important for my own wallet!) it should be affordable
I've looked into Google App Engine but for now I have decided not to go that direction. Main reason is the lack of a relational database.
For now I decided to go for a Grails or Ruby on Rails solution. I never developed a full Ruby on Rails application (except reading/trying some tutorials in the past) but maybe this is the time to give it a try... It's never bad to learn a new language and I think I will pick it up very quickly as it's concepts are very similar to Grails. I still need to think about this and will decide later which of the two I will use.
Based on hosting experiences within the Grails community I already made a shortlist of hosting parties and contacted them already with some question. This is my shortlist so far:
- eApps - e.g. Jan Sokol of grailstutorials.com is using this and is very happy about it
- Rackspace - there Cloud Server plans look great
- RimuHosting - also get good credits within the Grails community
I have some time to make a decision so any comments are appreciated.
Posted by
Marcel Overdijk
at
12:32 PM
10
comments
Thursday, May 28, 2009
Spring Roo coming alive

Spring Roo was announced just recently at JavaOne, and after the first alpha releases it's now time for M1.
If you are interested in this new "code generating" / productivity framework led by SpringSource you defintely have to read this introduction and example by project lead Ben Alex. Currently there is not much documentation available but this will change in the near future.
Similar to Grails, Roo wil have a plugin architecture using "add-ons". Looks like I've published the first community add-on - integrating SiteMesh - myself according to Ben's blog. Follow the steps below to try out the SiteMesh add-on:
- Follow the Roo installation instructions from Ben Alex's getting started blog post
- Download spring-roo-addon-sitemesh-1.0.0.M1.jar from http://jira.springframework.org/browse/ROO-41
- Copy spring-roo-addon-sitemesh-1.0.0.M1.jar to ROO_HOME\dist
- Start Roo and create a project as described in Ben's blog post
- After creating the project install SiteMesh to your project. Type 'ins' and press tab. Roo's shell will already display the availability of the install sitemesh command. Finish the command 'install sitemesh'
- That's it. The Maven pom file is updated so it contains the SiteMesh dependency. The SiteMesh filter and filter-mapping are added to web.xml. And default sitemesh.xml, decorators.xml and main.jsp files are created within your project.
- Open webapp\decorators\main.jsp to change your main layout and continue your project creating persistent classes, controllers, views etc.
It's really easy to create add-ons. If you are interested in creating your own add-ons have a look at the sources of the SiteMesh add-on or see the Roo core add-ons using Fisheye or SVN.
I think Spring Roo will have a bright future as it is led by SpringSource and primary uses best practices and boosts developer productivity. For companies/developers already using the Spring framework, Roo will be an easy and natural next step. This is a real strong point for Roo. Also integration with the SpringSource Tool Suite integration since day one will have huge benefits.
As a long time Grails adept I'm wondering how SpringSource will position both frameworks in the future. At least we have another choice for productivity again.
Posted by
Marcel Overdijk
at
10:59 AM
0
comments
