Introduction To Spring Roo 1.0.0

Introducing Spring Roo 1.0.0

Extreme Productivity in 10 Minutes

Ben Alex, Project Lead, Spring Roo

Copyright 2009 SpringSource. Copying, publishing or distributing without express written permission is prohibited.

Agenda

• Introducing Roo
• Capability Areas
• Using Roo
• Roadmap and Resources

Copyright 2009 SpringSource. Copying, publishing or distributing without express written permission is prohibited. 2

Agenda

• Introducing Roo
• Using Roo


Mission Statement

“Roo's mission is to
fundamentally and sustainably
improve Java developer
productivity without
compromising engineering
integrity or flexibility”


End User's Description

“Roo is a little genie who sits
in the background and
handles the things I don't
want to worry about”


What Is Roo?

• Roo is an extensible, text-based RAD tool for Java

• Roo is development-time only (no Roo runtime)


Implementation Overview

Roo Infrastructure

Roo STS
Roo
provide Add-Ons
Roo
@Roo Add-Ons
Roo
Add-Ons
Annotations Add-Ons
Shell

source only monitor and
retention change

User's Project

.aj .java .xml .jsp .properties


Easy To Learn and Use

• Usability you'll love
– “hint” and “help” commands to guide you all the way
– TAB completion for nearly everything
– Command hiding and automatic contextual awareness
– Even if you make a mistake, Roo will rollback changes!

• Scriptable UI that can even “replay” scripts

• You're in charge and Roo won't get in your way
– Roo acts predictably and conservatively at all times


Familiar Libraries

• Roo builds on what you already know
– Popular, proven, and mature APIs at your full disposal

• Java
• Spring Framework
• Java Persistence API (Hibernate)
• Java Server Pages
• Spring Security
• Spring Web Flow
• Log4J, Maven, AspectJ, Eclipse/STS...


Uses Java's Strengths

• The world's most popular language (Tiobe)
– Skills availability, vendor choice, low risks, open source

• APIs are popular, standardised, safe, proven

• Quality, mature and deep tooling integration
– IDE code assist, debuggers, refactoring, profilers etc

• Static typing
– Fewer errors, robust refactoring, code assist, JVM design


Cloud-Class Scalability

• Zero performance overhead
– Efficient, reflection-free code
– No dynamic proxies, deferred compiling, LTW or similar
– No Roo runtime means no runtime performance cost

• Zero memory overhead
– No class creation means no Perm Gen memory issues
– No Roo runtime means no runtime memory cost

• Zero deployment footprint
– Roo apps leverage OSGi bundles out-of-the-box
– No Roo runtime means no WAR footprint size


More Great Stuff

• No lock-in
– Get rid of Roo from your project in under 10 minutes!

• Easy to write and deploy your own Roo add-ons
– Roo can even write them for you (seriously!)

• Open source and SpringSource maintained
– SpringSource-endorsed application architecture

• Consistent apps across your team and enterprise


Code Generation Approach

• Roo is a hybrid code generator
– The best of the passive and active generation models
– Achieved by use case-specific design decisions

• Passive generation
– Use Roo shell to make Roo generate something
– It's done and it's finished (usually .xml and .java files)

• Active generation (automatic round-tripping)
– Builds detailed metadata model with help of @Roo*
– Incrementally updates .aj, .jsp files - never .java files


Active Generation

AspectJ ITDs

Person_Roo_
write Roo read Person.java
ToString.aj Roo
Add-Ons
Roo
Add-Ons
Roo name:String
toString():String Add-Ons
Add-Ons

Person_Roo_
JavaBean.aj
read AspectJ read
getName():String Compiler
setName(String):void

Person.class

write
Compilation unit separation name:String
toString():String
with automated round-trips getName():String
setName(String):void


Demo #1

The Roo Tour:

A Web App Without Reading The Manual

(or blogs, web sites, samples, pre-written code or similar)


Agenda

• Introducing Roo
• Using Roo


Out Of The Box

• Project management
• General object services
• Entity support
• Field management
• Persistence
• JUnit testing
• Dynamic finders
• Spring MVC, Spring Web Flow and Selenium
• JMS, SMTP and build system integration
• Spring Security, Logging Setup.....


Project Management

• Commands
– “project” → creates new project in current dir
– “dependency add” → adds dependency to POM
– “dependency remove” → opposite of add
– “backup” → creates ZIP of project

• All dependencies use Enterprise Bundle Repo
– Versioned, quality-checked, OSGi-compatible JARs


General Objects

• Roo annotations suitable for any class
– @RooJavaBean – getters and setters for free
– @RooConfigurable – adds Spring @Configurable
– @RooToString – you guessed it

• Roo will automatically maintain the code for you

• Roo won't get in your way
– It just sits in the background and writes code you don't
– You don't have to “tell” it to stop doing something
– You don't have to use the Roo shell (any editor will do)


Entity Support

• “entity” → creates an @RooEntity
– Delivers a flexible, feature-rich JPA entity
– Declares a JPA @Entity with id, version, EntityManager
and a no-arg constructor
– Automatically adds count, findAll, findById, findEntries,
persist, remove, merge and flush methods to an entity

• Command accepts many optional directives
– Whether to build an automatic integration test
– Table name, identifier column name etc


Field Management

• “field” commands for most major field types

• Field commands have options for
– JPA-specific annotations (--fetch, --column etc)
– JavaBean valiation-specific annotations (--max etc)
– Java modifiers (--primitive, --transient etc)

• Shell remembers last entity you worked with
– Fields are automatically added to that entity
– Override using --class


Persistence

• “persistence setup”
– Use --provider for Hibernate, OpenJPA and EclipseLink
– Use --database for most common databases
• Related commands
– “persistence exception translation” → via AspectJ
– “database properties list” → lists JDBC props
– “database properties set” → changes JDBC prop
– “database properties remove” → deletes JDBC prop
• You can re-run “persistence setup” at any time
– Switch from Hibernate to OpenJPA in one line!


JUnit Testing

• “test integration” → JUnit integration test
– Automatic “data on demand” feature for seed data
– This is implied with “entity --testAutomatically”

• “test mock” → JUnit mock test
– Allows test mocking of static methods in your entities

• “dod” → creates a data on demand class
– Rarely used directly
– Automatically created if tests require it


Dynamic Finders

• Saves you having to write JPA QL finders
– Roo will write them for you, complete with type safety!

• Finders are added as static methods to entities
– They're even compatible with abstract entities
– “finder list” → shows all available finders
– “finder add” → enable a specific finder


Easy Spring Web MVC

• “controller scaffold” → an automatic controller
– Automatic REST controller for a given entity
– Automatic JSP creation and maintenance
– Can fine-tune allowed methods (CRUD subset)
– Permits date format to be specified

• “controller all” → automatically scaffold all entities

• “controller class” → stub a manual controller
– Just the controller – you write the rest


Web Stack

• Automatic Spring JS, Tiles and URL Rewrite

• “selenium test” → Test a scaffolded controller
– Start Tomcat with “mvn tomcat:run”
– Then run the test with “mvn selenium:selenese”

• “webflow” → Create a flow with Spring Web Flow


Messaging: SMTP and JMS

• “email sender setup” → setup SMTP sender

• “field email” → adds an email sender field

• “jms setup” → sets up JMS support
– Optionally embeds a TCP-accessible ActiveMQ instance

• “field jms template” → adds a JMS sender field

• “jms listener class” → makes a JMS receiver


Build System Integration

• Assorted build options
– “perform clean” → runs “mvn clean eclipse:clean”
– “perform eclipse” → runs “mvn eclipse:eclipse”
– “perform tests” → runs “mvn test”
– “perform package” → runs “mvn package”
– “perform command” → custom mvn command
• You must have Maven setup and in path to use
• Often used at end of “script” files
– Verifies success
– Brings project into Eclipse for further work


Miscellaneous

• “security setup” → sets up Spring Security

• “logging setup” → sets up Log4J configuration

• “script” → executes a script
– Specify clinic.roo, wedding.roo, vote.roo and
bundlor.roo for inbuilt sample applications
– Specify a fully-qualified file system path for your files


Demo #2

Exploring “script clinic.roo”


Agenda

• Introducing Roo
• Using Roo


Requirements

• Java 5
– Same as Spring 3

• Maven 2.0.9 or above
– Roo itself doesn't need Maven installed to work
– Maven is only needed for Roo-generated projects
– ROO-91 requests Ant/Ivy → vote if you'd like it!

• Tested with Linux, Windows and Apple
– All platforms support tab completion and a colour shell


Download and Easy Install

• Download Roo from www.springsource.org/roo
– Simply unzip and add to your path

• Linux/Apple users would use something like:
– sudo ln -s $HOME/spring-roo-
1.0.0.RELEASE/bin/roo.sh /usr/bin/roo
• Windows
– Add %HOME%/spring-roo-1.0.0.RELEASE/bin to PATH

• A public Subversion repository is also available
– See readme.txt in root of checkout for dev installation


IDE Interoperability

• We highly recommend SpringSource Tool Suite
– Download it from www.springsource.com
– Totally free to use
– Includes Roo integration (eg CTRL-ALT-R commands)
– Also pre-bundles AJDT and other useful IDE plugins
• Eclipse also works, but use the latest AJDT
– Eclipse does not provide STS' Roo integration
– Roo can still be used concurrently via the shell

• Roo also happily lives alongside emacs, vim,
notepad, and no IDE at all


Lifecycle Notes

• SpringSource Tool Suite
– Use the embedded Roo option

• Any other case
– Load Roo at the same time as your IDE or text editor
– Roo automatically detects changes made outside Roo

• No need to add Roo to your build system
– Although “roo quit” will run Roo, update files and exit


Upgrade Actions

• When you upgrade Roo, .aj files may change
– This is a feature of active code generation
– We make optimizations and enhancements in .aj files

• Please refrain from editing Roo's .aj files
– Roo “owns” the *_Roo_*.aj files
– You can freely edit any file in your project except these

• Just “push-in refactor” any .aj files you wish to edit


Removing Roo in Three Steps

1. Use AJDT's “push-in refactoring” feature
– This moves the Roo .aj content into normal .java files
2. Remove Roo's annotation JAR from your POM
– You can use Roo's “dependency remove” command
3. Remove @Roo* annotations from .java files
– Use a regular exp find/replace in Eclipse for speed

• You can still use Roo on the project again
– Its “hands off by default” will ensure it's problem-free


Roo Internals

• “development mode” → full exception tracing

• “poll status” → auto-scaled file monitoring stats
• “poll speed” → adjust auto-scaled file monitoring
• “poll now” → force an immediate file scan

• “metadata status” → metadata statistics
• “metadata for type” → metadata summary
• “metadata for id” → metadata information


Add-On Services

• Third parties can easily publish new add-ons
– See the addon.roo script

• “addon list” → lists add-ons presently installed
• “addon install” → downloads and installs add-on
• “addon uninstall” → removes an add-on
• “addon cleanup” → refreshes the environment


Recommendations

• Use SpringSource Tool Suite
• Don't remove Roo from your projects
– You'll have much code to now manage by hand again
– You'll miss out on automatic upgrade improvements
– Consider removal as your insurance against lock-in
• Record your jump-start applications as scripts
– It's now so quick to change your design, so enjoy it!
– Defer custom coding until your model seems correct
• Ask questions on the forum for fast support


Demo #3

Roo IDE Integration


Agenda

• Introducing Roo
• Using Roo


Present Release

• Spring Roo 1.0.0.RELEASE

• Released 31 December 2009

• Extensive community feedback over 8 releases

• Plenty of documentation and tutorials included


Project Resources

• Home → http://www.springsource.org/roo
– Contains links to all other resources

• Forum → http://forum.springsource.org
– Roo team actively monitor forum and answer queries

• Issues → http://jira.springframework.org/browse/ROO

• Twitter → #roo hash key


Conclusion

• Roo delivers serious productivity gains for Java

– Popular, proven technologies you already know
– Easy to learn and easy to use
– Builds on Java's strengths
– Extreme performance
– No runtime, no lock-in, no risk

• An active, supported, open source project

• Questions? balex@vmware.com


Introduction To Spring Roo 1.0.0

Recomendados

Recomendados

Más contenido relacionado

Similar a Introduction To Spring Roo 1.0.0

Similar a Introduction To Spring Roo 1.0.0 (20)

Último

Último (20)

Introduction To Spring Roo 1.0.0