Comments on: Why Spring Roo is not my thing

By: Greg

Greg — Fri, 07 Oct 2011 15:53:43 +0000

Roo is a definite time saver for boot-strapping projects, especially for the data access tier. It also is a time saver for boot strapping the controllers and JSPs because it builds in the spring context wiring and support for I18n and it does it the “right” way so you have great examples to work from. Just as an FYI, I have several large projects running in production that were originally boot-strapped from Spring ROO.

That being said, forget about the UI (jsps) ROO generates. Just use the controllers as templates and build your own UI. I was very surprised to see ROO uses dojo instead of jQuery for the javascript libraries, maybe it’s a licensing thing? Every company I’ve ever worked for uses jQuery but that is just my personal opinion.

Lastly, I totally don’t get the argument, forget about the IDE and give me a good text editor and command line. Apparently those that subscribed to this point have the entire JDK memorized as well as every 3rd party library used in their apps. Not to mention code searches, visualizing class hierarchy structures, etc. Really, let’s just use a good text editor?

By: hafsa

hafsa — Thu, 29 Sep 2011 17:40:58 +0000

I feel ROO is amazing
A very article aboutt RO
http://eiconsulting.blogspot.com/2011/09/spring-roo-amazing-framework.html

By: rajesh

rajesh — Thu, 11 Aug 2011 13:50:02 +0000

We have this requirement of using gwt with spring and hibernate in medium weight project.A proposal has been placed of using roo to combine all these frameworks.I am still fuzzy of this proposal as we have to stick with scaffolds of roo and of course aspectj and compositions as mentioned in this article goes against it.But there is sense of urgency from our clients and everyone is speaking of roo.So a simple question to all the experts here whats your opinion and any other suggestions that proves way worthy than the current one.
Thanks for any replies.

By: Maciek

Maciek — Tue, 05 Jul 2011 20:12:12 +0000

Well, I must agree that composition thing sucks. JSPs not a problem for me, i change them completly anyway. I also think that interface as it is is quite useless up till now. still, quite nice tool, and probably the future is somewhere in it.

By: jettro

jettro — Fri, 20 May 2011 11:14:34 +0000

Well we are 2 years after the blog post and I still don’t like it. So I guess I was right. A lot of other people do like it. That is for sure.

By: zerolinesofcode

zerolinesofcode — Thu, 19 May 2011 07:30:10 +0000

Time will tell you were wrong.

By: Stephane

Stephane — Wed, 20 Jan 2010 14:00:41 +0000

What would be nice is to be able to add to an application, some lean libraries that focus on one thing each.
I would like to be able to create an application with a tool like Roo, only to create it fast, then forget about Roo and code it further in Spring. I would then use a gorm.jar helper library to give me dynamic finders, and a coc.jar helper library to give me conversion over configuration so as to allow me not to explicitly wire up my application controllers with annotations (no Spring autowiring). And of course, all of this available on the command line. Coding with an IDE is a pain in the… neck. The name resolution offered by Roo on the command line is superb ! This name resolution is enough for me to ditch the IDE. I’d say Roo is one step done right. One more and we can dance !

By: Jonathan Woods

Jonathan Woods — Fri, 15 Jan 2010 10:31:57 +0000

For people not seeing AspectJ tooling working: don’t forget that your IDE needs to know aspects are involved. I’m using Eclipse, and found that using perform eclipse in the Roo shell gave the Eclipse project its AspectJ nature, and then lo! code completion etc all worked fine.

By: Ken Rimple

Ken Rimple — Fri, 11 Dec 2009 14:30:14 +0000

Nope, same as before. As long as you don’t try to use ITD methods (like entity weaved methods such as find, etc) from java classes, the compiler doesn’t complain. But then that means writing real code with the tool will generate compiler errors. So until the AspectJ plugin for IntelliJ has ITD support we’re where we were.

By: Ken Rimple

Ken Rimple — Fri, 11 Dec 2009 00:48:00 +0000

I am the cause of that confusion. Didn’t realize what I wrote in that blog entry and have to go back and correct it.

That entry that says that IntelliJ ‘works pretty well’ with Roo was mine – at the time I was experimenting with the framework and seeing what could edit the files. The problem I had was that I got build errors, and it didn’t support ITDs directly. I was building using Maven and using IntelliJ as a text editor at that point.

I am testing Roo RC3 and the newly released IntelliJ 9.0. It seems to be working (at least not giving me errors on the annotations). I’m going to mess with it and post an updated blog entry.

Sorry for creating confusion.