This document compares and contrasts three tools for developing Spring applications: WaveMaker, Spring Roo, and SpringSource Tool Suite. WaveMaker is a visual tool for quickly creating standard web apps without coding. It generates a Spring-based backend and uses JavaScript for the frontend. Spring Roo scaffolds Java and Spring code to reduce boilerplate. SpringSource Tool Suite is an Eclipse-based IDE that enhances the Java experience for Spring projects. The document recommends combining WaveMaker for frontend development and Spring Roo/SpringSource Tool Suite for backend development, and making it easy to use both tools together on the same project.

1. WaveMaker – Spring Roo –
SpringSource Tool Suite
Choosing the right tool for the right job
Martin Lippert
mlippert@vmware.com
© 2011 SpringSource, A division of VMware. All rights reserved

2. Speaker Introduction
§ Martin Lippert
• Senior Member Technical Staff, R&D
• Lead, Spring Development Tools
2

3. The landscape
WaveMaker
Spring Roo
SpringSource Tool Suite
3

4. WaveMaker – a quick look
§ It’s some kind of 4GL tool for web-apps
• You can quickly create standard CRUD apps
• drag&drop and visual editors, no real coding
• Produces a JavaScript based web app
• you can implement stuff yourself (JavaScript for the front-end and
Java for the back-end), but that should be a rare case
§ Behind the scenes
• Generates a Spring-based web app
• Uses lots of JavaScript for the app
• Is focused on the front-end, Java experience is poor
• Will use Spring Roo under the hood (not yet there)
• Is open-source and itself web-based
4

5. WaveMaker
Demo
5

6. Spring Roo – a quick look
§ Scaffolding for Spring developers
• Let the expert Java and Spring developer to the “real” work
• Generates the boring stuff for you, like
• Models and mappings
• CRUD services
• Basic web UI (mvc, gwt, others)
• Produces a regular and good looking Java/Spring project
• Is an addition to the Java/Spring IDE, not a replacement
§ Behind the scenes
• Produces Java and AspectJ code
• Command-line interface or IDE integrated
6

7. Spring Roo
Demo
7

8. SpringSource Tool Suite – a quick look
§ Eclipse-based full-featured IDE for Spring developers
• Focused on coding productivity
• Enhances the Java experience of Eclipse to Spring projects, including
• Content-assist, validation, quick-fixes, visualizations, navigation, etc.
• Integrates Spring Roo, tc Server, Maven, Groovy/Grails, Gradle
• Direct Deployment to Cloud Foundry, incl. full debugging support
§ Behind the scenes
• Compatible with Eclipse Indigo and Helios
• “old style” desktop IDE
8

9. SpringSource Tool Suite
Demo
9

10. Comparison
§ Spring Roo / SpringSource Tool Suite
• Expert Java developers
• Code-centric
• Good at Java/Spring code
• Poor support for UI development and JavaScript
§ WaveMaker
• Non-programming experts
• Visual programming
• Good for rapid web app development, web UIs and JavaScript
• Very poor Java experience
10

11. Combining the tools
The key is to combine the tools
Using WaveMaker for web UI and JavaScript
&
Using Spring Roo & SpringSource Tool Suite for JVM-
centric back-end development
11

12. Combining the tools
Demo
12

13. Outlook 1/2
§ WaveMaker:
• tooling for frond-end development
• Modern web apps
• Based on JavaScript
• Single page style architecture
• Accessing RESTful APIs
• (not focused on implementing services)
§ Spring Roo + SpringSource Tool Suite:
• Tools for expert JVM developers
• Mostly for back-end services
• JVM-based development
• Spring-enabled, but not exclusively
• Focused on code productivity
13

14. Outlook 2/2
§ Make it easy to use both tools together
• Within the same team
• For the same app or project
• No pain of importing/exporting stuff
14

15. Thank You
Q&A
Martin Lippert
mlippert@vmware.com
@martinlippert
15