Is Spring the right tool for me? (See List of job requirements)

Question

I watched several videos, Roo demo and I liked it. However, before starting to use it, I would like to ask some more experienced programmers with Roo.

• Roo uses a lot of AOP. Is it possible to write my own Java code and let Roo generated files just "be alone"? Or the whole structure of Roo requires some knowledge of AOP. In other words, if I want to set up a Roo project (add non-CRUD functions), do I need to mess with AOP?

• I saw a console approach for generating objects. Can Roo convert my database that already runs in Roo code (generate entities for me)?

• Sometimes I have big entities. I do not want to show specific columns in the user interface. Is such a setup easily achievable?

• Getting current views - I would like to do some export of what the user sees right now in the user interface (say, in XML). Auto export will be great, but at least I can easily get the current data in the user interface view? (let's say the user sees 10% of the data in the DB table, I would like to save it in XML)

• My database often changes. How does Ru go with changing entities? This is the dynamic addition / deletion of certain columns ...

• Import data (or whole new databases). I need to drop and create the database on the fly. Thus, the user interface may change slightly (new columns), and the data will necessarily change. Will it work with a simple “run script and update”?

• Rollbacks. Discard your changes. Does it provide built-in support for such a thing?

• Reporting, or at least integration with popular reporting tools.

And what do you think? Does Ru match? Should I try? Or am I better off starting from scratch using simple GWT, JSF, what?

OT: Seeing these requirements, feel free to comment on which Java framework you have chosen. Now I think of GWT (I know this kind of thing), JSF or Spring Roo (no, I don’t plan to write JavaScript UI myself); -)

Answer 1

Here are the answers to my knowledge of Roo:

1.Roo uses a lot of AOP. Is it possible to write my own Java code and let the Roo generated files just "stay alone"? Or the whole structure of Roo requires some knowledge of AOP. In other words, if I want to set up a Roo project (add non CRUD), do I need with AOP?

No, you do not need to mess with AOP. Most files created by Roo (for example, .aj, etc.) can be left alone, except for the files in which you put the code.

2. I saw the console approach of generating objects. Can Roo convert my database, which already runs into Roo code (generate objects for me)?

Yes, [check the steps for restoring Roo engineering] [1].

3. Sometimes I have big entities. I do not want to show specific UI columns. Is such a setup easily achievable?

Yes.

4. Getting current views - I would like to make some export data of what the user sees right now in the user interface (say, in XML). Auto export will be great, but at least can I easily get the current data in the user interface? Look? (let's say the user sees 10% of the data in the DB table, I would like to save it in XML)

Yes.

5.My database is often changing. How does Ru go with changing entities? This is the dynamic addition / deletion of some columns ...

Send my answer to question 2.

6. Import data (or whole new databases). I need to drop and create databases on the fly. Thus, the user interface can change the bit (new columns) and the data will necessarily change. Will this work with a simple “run script and update”?

Yes

7. Rollbacks. Discard your changes. Does it provide built-in support for such a thing?

No. No rollback support. There is an expected function request for this. However, there is work around.

8. Registration, or at least integration with popular reporting tools.

This will not be different from any of your regular Java applications just because you use Roo.

And what do you think? Does Roo match these? Should I try? Or am I better off starting from scratch using simple GWT, JSF, what?

Hope the answers above explain!