Is Spring Roo just for building a site skeleton?

Question

After many problems, I finally installed Roo with a simple example.

Now I just want to know how far to go with Roo.

I mean fields, classes, everything can be done through the Roo shell.

Now, for example, I have 15 classes in my project. I am confused - at what point should I make classes with the Roo shell, and when should I leave Roo and start working as usual?

In addition, Roo has its own graphical interface and layout. Can we also change this?

Answer 1

ROO , , Scaffold, , . , , ROO, ROO .

Answer 2

Telosys Tools, - .

, Spring Roo,

Spring MVC Spring : https://sites.google.com/site/telosystutorial/

Answer 3

I agree that the Roo Scaffold application is that structure: that you can use to create your own application, but this is not something you would like to expose as a client in your own right. So far, I have used Roo to create or modify a data model and let it manage and modify most of the code that is needed to interact with the data model. But any work that I do outside the model, I do myself.

My advice: use Roo where its power is, and then do the rest manually.