Learning Spring Roo without running from entities

Question

I just started learning Spring Roo. After reading the creation of a web application in 10 minutes. I got the impression that Roo assumes that we have an entity concept, and create a controller component - or what they call the stage.

We are at the prototyping stage, and we are splitting the task of exploring a user interface component and a constant layer between two people. On my side, I am trying to create a simple user registration form that accepts a username, password, sends a request to the server and gets the server redirected to another page.

Is there a good approach for this task without creating objects, as described in a 10-minute lesson: http://static.springsource.org/spring-roo/reference/html/intro.html#intro-first-steps

I downloaded the Spring Toolkit (STS), and I'm trying to run roo, maven, functions in STS to get started.

Any tips, tricks or useful links to another tutorial are welcome. Thanks.

Greetings

Answer 1

Yes, it’s called breaking the scaffold and manually encoding the pages and controllers that you need, servlets if you need them (which you usually don’t). If you use Spring MVC (ui by default, if you do not use GWT), then it is as simple as adding your own controller to the list, which processes POST and GET requests, passes parameters back to the interface using the Model Object, updating the views to display your pages, and then if you still want to use the created roo scaffold for certain things, you can move the pages on which it is displayed.

http://static.springsource.org/spring/docs/3.0.x/reference/mvc.html

Answer 2

You will need to create entities / classes. You will need to have a basic class diagram that you can use to get started with ROO to create the main Java application.

If you are concerned about how more than one person will work on it, then refer to this SO stream .

Hope this helps.

Answer 3

I recently started learning ROO. And based on what I understand, entities are central to ROO.

• For each object you add, you can use ROO to add a controller for that object.
• For each added controller, ROO automatically generates Create, List, Show, and Update views (using jspx, Dojo JavaScript lib, and spring-js). Roo also installs the tagx library, which is used by all generated views.
• In views, ROO adds a form field for each field that you defined in the corresponding object.

So, back to your question. Start with the entity model that you end up with. Then use ROO to create an object that will be used to store user registration information, and add a controller for this object. At this point, you can start learning about the user interface component, and another person can start adding entities (without adding controllers, so no view will be created) that you need, and study the save layer.