So I recently had need to package up a Spring Roo Java application so that it could be run by someone else remotely. Now most SpringRoo apps I know are web apps - deployed as WAR files to a web server like Tomcat. But I was asked to make sure it ran from the command line. The main problem I had was that all my third party jar files are stored in my local Maven repository.

In my previous two tutorials we produced something that responds to REST requests like this:

  GET http://myhost:8080/longurl/urlmaps/[url_id]
  Accept: application/json

But that isn't very useful when looking back at my requirements. I really want to send a URL as a parameter - not its id.

So in my last article in this series I talked about creating a basic REST server with Spring Roo. Here I start running the server and testing it.

For some time now I have been impressed with a tool called Spring Roo. This helps me create Java applications with the Spring Framework. Here are some of the articles I have written about it.

Spring Roo Add Ons: Typical Security

The idea behind Spring Roo is that you tell it what you want, and it gives you a Java and Spring framework for developing such a tool. Typically the app you are building is a website (though it doesn't have to be).

One of the most common features of a web application framework is some kind of role based permissioning mechanism. As well as the ability to store users details, we also want to store jobs (or "Roles") that users might do, and record which users are authorised for which roles.

Here is a review of a book I bought while still in "Early Adopters get the incomplete ebook" phase. Spring Roo Cookbook from Packt Publishing.

You may remember my article some time ago written about Spring Roo. Well I've been playing with it some more and am thinking that the pros outweigh the cons.