Roo development - meandering path?

[Chanoch]

I've been going through the various Roo tutorials trying to eek out a development methodology from the system, but it seems to me there are a few pointers that Roo is a one-way development process. What I mean is that if you've auto-generated a unit (like a field or class) and forgotten one of the switches (such as testAutomatically), the only option for refinement is to find the affected files, delete the affected areas and then redo the command.

Is that correct? I'm wondering if this is essentially a design choice within Roo and what the reasoning is?

thanks

chanoch

[krimple]

While it certainly is true that setting up a new feature in a Roo application, such as Spring MVC, is not undo-able, you should probably back up your application (or better yet, use Git and do a local branch to experiment) each time you configure a new feature.

However, I want to correct what you said about the --testAutomatically option. That statement is incorrect. You can just do this:

test integration --entity ~.model.MyEntity

That will create the integration tests, DataOnDemand framework, and watch for changes to your object.

Also, if you move to using Repositories and Services, the integration tests will switch to using them.

Ken