What’s next

June 18, 2009

Simple REST server with Grails

Filed under: Architecture,Grails,Groovy — stigl @ 11:36 am
Tags: , , ,

I have recently worked on two small projects that need a simple data store for more intelligent clients. Choosing REST was a no-brainer after some discussion. Grails’ HTML CRUD interface is a great template to start off with, but it lacks dealing with XML/JSON.
(more…)

December 6, 2008

Groovy does Neo4J thanks to Maven Simplicity

Filed under: Groovy,Java — stigl @ 11:54 pm
Tags: , , , , ,

Guillaume Laforge, Groovy Project Manager, kicked off a debate on the Neo4J mailing list with his post Groovy and Neo4J. He stated some examples of how Neo4J could be more Groovy. However, since most Neo4J developers aren’t familiar with Groovy, the topic wasen’t tested out further.

Therefore, with of my L337 skillz in Groovy, Neo4J and Maven, I saw it my destiny to create a simple Neo4J test in a Groovy environment to validate Guillaume’s propositions. Along the way, I had to add some GMaven magic, embedded Neo4J, Mercurial version control and Maven Archetype for distribution. No wonder why I didn’t get this out the door yesterday! 😉
(more…)

November 12, 2008

Grails 1.1 got Maven support – So What?

Filed under: Groovy — stigl @ 12:07 pm
Tags: , ,

You know you’ve been wasting too much time blogging in the sphere when, renowned developers start stalking YOU 🙂
Anywho, the comment I recieved informed me that Grails 1.1 Maven support is out, giving Maven developers much needing air-mileage towards a Grails firstclass-citizen-goldcard. Predecessor Octo was, what I reckon, a shell around Ant scripts for doing Grails tasks, distancing Maven from responsibility of doing the nitty-gritty building and wiring.

So why should you care who builds your Grails project?

Because of the nifty reusable plugin functionality you get out of the box from maven. And more importantly with Grails, control of how you wire your app together.

The current state of the new Maven plugin

I can’t see no Ant anywhere. It might be because I’ve been lazy and havent poked around the poms, but until contradicted, I choose to believe that Maven is in charge. One difference is the added folders, src/main/webapp aso. Does it work as it should yet? Of course not, it wouldn’t be bleeding edge if it did, but well enough for me to get a good impression and a list of issues to report back on.

Conclusion

If the Maven plugin picks up speed inside GrailsDev, I’m a happy camper! Good Work!

October 27, 2008

MicroXP just made Windows sexy for development

Filed under: Groovy,Java — stigl @ 1:58 pm
Tags: , , , , ,

There are times you have an application or job task which requires windows, and you need a Windows box with the least amount of hassle and small footprint.

Behold MicroXP; a stripped down version of WindowsXP. Match weight: 100MB distro, <500MB HDD, <50MB RAM, ~10min almost inputless installation and <20 second bootup time!!!

Just to test it out for development in parallels, downloaded Java 6 JDK, Maven and tested out the Smacking up Groovy demo in less than 10 seconds which creates a full Java/Groovy development environment with no hassle. And it worked!

Conclusion: Damn sweet footprint! You can propably get your chores done, and still be smiling. Bill Gates won’t love us, but since when has he appreciated Java anyways?

PS. I have been using OS X for over a year, and allthough MicroXP is sweet and sexy, I’m still content with having moved away.

October 11, 2008

Smacking up a Groovy demo in less than 10 seconds

Filed under: Groovy — stigl @ 1:39 pm
Tags: , ,

Write mvn groovy:console , and you will get a console where you can execute Java/Groovy code by typing ctrl+enter/+enter.

If I were to learn a new language, or Java from scratch again in the University, This way of packaging would make a HUGE difference!

What next?

The sweet spot for using Groovy is

  • Familiarity to Java developers. Paste in your favorite Java code, and it will compile
  • Java classes are imported and used as normal
  • Strings, Files and many other standard classes have been extended with often-used functionality
  • Handling stuff on the file system – copying, deleting aso
  • Parsing XML in a nice DSL
  • Simple SQL/JDBC
  • Binding together a Java application

Resources

September 30, 2008

What I’m into right now

I thought I’d post updates on what I’m interested in, to give a glimpse of what I’m looking into and have moved away from. Perhaps I’ll have enough data to create a graph someday 🙂

Up and coming

  • Neo4J – A graph store – no more ORMappings
  • Qi4J – A composite development framework, a new way of writing Java applications, a way of life
  • Groovy GRAILS – Excellent for prototyping Java stuff
  • Mercurial – When thinking different, why not Version Control as well?
  • Swing Appframework, Java6u10 – Propably the next big thing in Rich Internet Applications
  • Visualization of graphs – Am looking for a nice, easy API for creating several hierarchical trees that I can drag and manipulate
  • Amazon EC2 – Java enabled servers on demand!
  • Twitter, Blog, IRC -New (and revisited) ways of communicating intra-project/company
  • javaBin, JavaZone – Working with the JavaZone conference for a year was damn fun!
    (more…)

June 27, 2008

Reading up on Groovy and Grails

Filed under: Groovy,Java — stigl @ 9:27 am
Tags: , , , , ,

The good thing about Groovy is its likeness to Java, and reading Groovy code should pose no difficulty to a seasoned Java programmer who’s taken a days worth reading. The problem with Groovy is writing good code. Not because you do it wrong, but you can always write it better! As with Ruby, there are alot of nifty features in the language that shortcuts ugly code in Java. But, you have to know that these features exists before you can use them. Grails? It just might become the next dogma in Java application development!

This is the litterature list and resources I’ve used in my pursuit of becoming a Groovier developer:
(more…)

June 13, 2008

Dissecting Grails for Maven building

Filed under: Groovy,Java — stigl @ 11:40 pm
Tags: , , , ,

Show me your war, and I will tell you how it does!

Upgrading a Java project from a legacy buildsystem to Maven involves lots of reverse engineering to understand how the application works. Starting to investigate a project by its deliverables is often the most easy, taking a working application and picking away piece by piece, like dissecting a frog, to see if it still works after some abuse and halfchanced guesswork.

I started by grails create-app‘ing a simple book tutorial grails app, and grails war‘ing it. The contents of the war were extracted into src/main/webapp of a maven demo project, supported by groovy-all, GMaven (Groovy Maven plugin) and Maven Jetty plugin. (more…)

Create a free website or blog at WordPress.com.