AI tools

Spring Roo

Open-source software tool From Wikipedia, the free encyclopedia

Spring Roo

Spring Roo is a open-source software tool that uses convention-over-configuration principles to provide rapid application development of Java-based enterprise software.[1]

Quick Facts Developer(s), Final release ...
Spring Roo
Developer(s)DISID, Pivotal Software
Final release
1.3.2 / September 1, 2015 (2015-09-01)
Preview release
2.0.0.RELEASE / September 30, 2019 (2019-09-30)
Written inJava
PlatformJava SE
TypeRapid application development
LicenseApache License 2.0
Websitegithub.com/spring-attic/spring-roo
Close

The project has been deprecated and active development has ended.[2]

Motivation and history

Summarize
Perspective

Spring Roo's mission statement is to "fundamentally improve Java developer productivity without compromising engineering integrity or flexibility".[3]

The technology was first demonstrated during the opening keynote at the SpringOne Europe developer conference on 27 April 2009, with an initial alpha release concurrently being published. During the keynote an application was built live on-stage that would be used by conference attendees to vote on the preferred name for the project (which at that time was codenamed "Roo" within SpringSource).[4] Ultimately the name "Spring Roo" was preferred over alternatives including Spring Boost, Spring Spark, Spring HyperDrive and Spring Dart.[5]

Several releases followed,[6][7] with the Roo 1.0.0.RELEASE (general availability) released in December 2009. In October 2010, Spring Roo 1.1.0.RELEASE was released. The 1.1.0 release moved to an OSGi foundation with associated add-on discovery model, plus added support for incremental database reverse engineering, Spring MVC page complexity reduction, Google Web Toolkit, Google App Engine, Apache Solr, JSON and smaller features like serializable automation.[8]

In 2014 DISID took over the leadership of the open source framework Spring Roo after a partnership agreement with Pivotal.

DSID and VMware deprecated Spring Roo and announced the end of active development in 2019 and the repository was archived in 2022.[2]

Standards and technology compatibility

Summarize
Perspective

Roo's default installation facilitates the creation of applications that comply with the following standards and major technologies:[9]

The above list can be augmented through additional Roo add-ons, which provide Roo's method of extensibility.

User interface

Summarize
Perspective

Spring Roo's main user interface is a command-line shell. The shell provides both a command-line interface and also a mechanism to host plug-ins (which are called "add-ons" in Roo). One key design goal of Roo is to ensure a user can continue to work in a "natural way", which typically means using their preferred integrated development environment (IDE) or text editor for most tasks. As such Roo is often loaded in a separate window to the IDE or text editor, and will monitor the file system for changes made by the user outside of Roo. A startup-time scan of a user's project is also performed to determine any changes that may have been made while Roo was not running.

The user interface shell supports extensive usability features including command-line completion (i.e. press TAB), online help, hinting (a form of context-sensitive help) and contextual awareness (which provides automatic inference of likely intentions based on recent activity). This allows a user to create a new software project via the Roo shell, or use Roo on an existing project. The following is an example of the commands used by Roo to create a new application plus the Spring Boot Maven plugin run goal to compile and run the application using an embedded HTTP server:

$ mkdir hello
$ cd hello
$ roo.sh
roo> project setup --topLevelPackage com.foo
roo> jpa setup --provider HIBERNATE --database HYPERSONIC_IN_MEMORY
roo> entity jpa --class ~.domain.Timer
roo> field string --fieldName message --notNull
roo> repository jpa --all
roo> service --all
roo> web mvc setup
roo> web mvc view setup --type THYMELEAF
roo> web mvc controller --all --responseType THYMELEAF
roo> web mvc controller --all --pathPrefix /api
roo> quit
$ mvn spring-boot:run

The above commands did not need to be typed in full, but rather were completed using TAB. Additionally, the "hint" command could have been used to acquire help at any time.

Architecture

Roo operates by generating AspectJ inter-type declarations (otherwise known as mixins or introductions). This achieves separation of concerns, as the code maintained by Roo is in a different compilation unit from the code a user writes. This means Roo can incrementally modify the AspectJ inter-type declarations that it needs to and leave all other files intact.[11][12][13]

Spring Roo uses add-ons to provide all the functionality within and on top of an OSGi runtime system based on Apache Felix.

Differentiation

Summarize
Perspective

Spring Roo differs from other convention-over-configuration rapid application development tools like so:[14]

  1. Java platform productivity: Roo provides a productivity solution for Java developers. It does not require the user to program in any language other than Java. It also uses mainstream Java enterprise application standards and technologies (as listed above) to maximize reuse of existing developer knowledge, skills and experience.
  2. Usability: Roo's shell is designed to provide a discoverable, easy-to-use environment that minimizes training requirements. Roo annotations all start with @Roo to facilitate code assist (command line completion in IDEs). Users can use their IDE for all operations and do not need to be aware of Roo running. Roo also supports users editing their files when Roo is not running.
  3. No runtime: Roo does not provide a runtime API or require specific runtime components. This ensures there is no Roo-related CPU, memory and disk storage resource consumption at runtime. Roo code is optimized for small-footprint cloud deployment and high scalability use cases.
  4. Avoids lock-in: Roo can be rapidly removed from a user project, which is useful to protect against vendor lock-in. This is possible because there is no runtime component to remove, @Roo annotations are "source retention" only (ensuring they are not preserved in compiled *.class files)[15] and Roo's AspectJ inter-type declarations can be "pushed in" to standard *.java compilation units.[16][17]
  5. Extensibility: Roo's separation of core infrastructure and base add-ons intends to allow third parties to easily extend Roo.[18][19]

See also

References

External links

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.