Position with Spring Roo

[Steren]

Hi Players,

It's the first time I talk on this list. First of all, thanks a lot to you, the PlayFramework devs and community, for what you are doing.

Now, it has been my framework of choice for personal projects. We are currently building the future Beansight website using Play!.

I had a small look to Spring Roo since the GWT team announced the next version will work closely with it. and I have some interrogations:

* What is the position of Play toward Spring Roo ? They look very similar in the way of using Java for rapid and efficient web dev.

* Does anyone have experience with Spring Roo ? Can you tell us what you think about it ?

* What are the differencies ?

* Do you think that if Google has chosen Roo to be almost shipped with future GWT version, this will lead high popularity ? Can it be a negative point for Play! ?

* Will we be able to easily plug Play! on the MVP framework of the next release of GWT ?

This message is not about competitiveness, it's just to answers questions of a non java guru who appreciates GWT to build complex webapps.

Thanks again for Play!

Cheers,

Steren

[Julien Tournay]

Hi,

Roo and Play! aren't really comparable.

Roo is a code geneation tool. The idea is to generate code that uses Spring / JPA / AspectJ etc. to build a webapp.

Play! aims to make the code easier to write, but doesn't relly on code generation (for example there's no scaffolding like in rails).

The goal is pretty much the same (dev webapp faster), but the philosophy greattly differs.

jto.

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.

--
Real Programmers don't need comments-- the code is obvious.

[Pascal Voitot Dev]

I spent 1 month on Roo before discovering Play!...
I had used grails a lot but grails doesn't work with Google App Engine...
I discovered Roo and was wondering if it could be used with GAE even if I really think Spring stuff are becoming really too heavy for developing simple applications such as web application 90% of the time.

Roo is nice in theory: a kind of Grails for Java but with a difference: everything is compiled before runtime whereas Grails compiles at runtime... great difference in fact :)
When I saw it, I was really happy but I soon changed my mind...
At the beginning, the code generation concept is cool but becomes soon a complete coding horror...
Everything is generated with AspectJ and you don't have any control on the code anymore...
This is not your code but Roo code and moreover, this is no more Java code but AspectJ!!!

I wonder why they chose to do everything with aspects even if it seems nice on paper!
So I agree, the goal is the same, the philosophy differs!

Roo is also very young and I had some compatibility issues between 2 versions.
When I discovered Play! by chance and after spending one week on it, I said:"this is my solution"...

regards
Pascal

[Daniel Guryca]

Exacatly !

Year ago I was making a decision which framework to choose for our company.

Grails was nice but too buggy, too slow and too Groovy dependent (which I did not like).

Roo was very very young. I did try it too had same feeling as you - AspectJ everywhere - did not like.

Play was and is a winner for us.

Daniel