Will you plz tell me how we create Tabs, Menu Bar & Check boxs all these tools in Spring Roo project. Please reply me as soon as possible.

Thanks in advance

Any comments?

Glad to here that reverse engineering is one of the features in following releases. And the thing about reducing jsp size sounds interesting, can't wait to see that ! (and I'm very curious where roo 1.1 will show up?)

I have one more question regarding application organization. When I have roo based application, and I want to add some business logic into it, where to put that code? For example, if I wanted to do some business calculations before saving a bean into db, where to put that logic?

Applications that we work on are layered organized, we have controller layer, service layer (where we put business logic) and DAO layer (using GenericDAO). Service layer starts transaction, because we usually don't save just one object, we save a lot of them and we sometimes have complex business logic which decides what and how will be saved.

So my questions is: how to deal with this things I mentioned above in roo based apps?

Regards, Boyan

Database reverse engineering is something we are currently working on and you will see the first incarnation of it with the Roo 1.1 release.

We kept the create and update jspx pages separate for two reasons. First, many users actually want to present different pages for the create and update cases. For example, you might not want certain fields to be updatable once they are created (with separate pages you can simply disable these fields in the form). Second, there are a number of technical aspects which are easier to handle and understand if you keep them separate (form submission URLs and types (POST, PUT), hidden params, button labels, etc.

Of course, if you wish to maintain only one form for both you can simply change the view name returned by the updateForm method in your controller to the same name as the createForm. Roo will not get in your way if you wish to do this (just push in the relevant methods into your Java sources).

Also, you might be interested to hear that with the 1.1 release the generated forms are reduced in size by about 85% which will make it a lot easier for you to maintain two forms, even if they are mainly the same. All fields and forms will actually be in reusable JSP tag files and therefore adhere to the DRY principle.

Hope this explains our default choice for the separation of create and update forms.

Stefan Schmidt
Spring Roo Software Engineer
SpringSource, a division of VMware

The thing which is missing is database reverse engineering, without that roo is quite unuseful. For example, if I had database containing 40 tables, each of them had 10 columns, that makes 400 properties to write in roo script. But I heard this option will be added in version 1.1.

Another thing I don't like are generated jsp(x) pages. Actually, they are ok, but I don't understand why there are create.jspx and update.jspx page. In our project, when we wrote CRUD manually we had one page for both create and update operation. On roo case there are two pages for these operations, so if I had to manually add some code, I had to add it in both create.jspx and update.jspx. I compared these two files, and they are almost the samo.
Can anyone tell me reason for such behavior?

=========================================================
null
Error
Mon Feb 08 10:40:58 EST 2010
Internal Error

java.lang.reflect.InvocationTargetException
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:121)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.core.runtime.CoreException: No valid Spring Roo installation configured. The Roo version must be at least 1.0.0.RC3.
at com.springsource.sts.roo.ui.internal.wizard.NewRooProjectWizard$1.execute(NewRooProjectWizard.java:163)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
… 1 more
Caused by: java.lang.ClassNotFoundException: org.springframework.roo.shell.ExitShellRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:315)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at com.springsource.sts.roo.ui.internal.wizard.NewRooProjectWizard$1.execute(NewRooProjectWizard.java:160)
… 4 more
Root exception:
org.eclipse.core.runtime.CoreException: No valid Spring Roo installation configured. The Roo version must be at least 1.0.0.RC3.
at com.springsource.sts.roo.ui.internal.wizard.NewRooProjectWizard$1.execute(NewRooProjectWizard.java:163)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.lang.ClassNotFoundException: org.springframework.roo.shell.ExitShellRequest
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:315)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at com.springsource.sts.roo.ui.internal.wizard.NewRooProjectWizard$1.execute(NewRooProjectWizard.java:160)
… 4 more