springojs | SpringoJS lets you use RIngoJS

springojs is a Java library. springojs has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However springojs build file is not available. You can download it from GitHub.

SpringoJS = Spring + RingoJS!. Springo provides a minimal framework for incorporating RingoJS into a Spring MVC application. Note: RingoJS is built on top of Rhino a very mature Javascript engine that runs on the JVM. In what follows I will sometimes use "Ringo" and "Rhino" interchangeably. In reality Ringo is a superset of Rhino that adds (node.js style) CommonJS module support to Rhino, along with a variety of modules including an express-style middleware framework called "stick". The result is a very node.js-like framework that runs on the JVM with the biggest difference being the use of java style blocking I/O which avoids the frequent use of callbacks as seen in node.js. The approach used in Springo has been used quite successfully at a fortune 500 company to deliver RESTful JSON services using a codebase that started as a Java Spring application, but evolved into a "hybrid" Spring + Server-Side Javascript application using both Spring MVC and Ringo/Rhino running together within a single JVM process. In this approach we found Ringo's server-side Javascript to be very productive and brought a "rapid application development tool" flavor to our RESTful service development compared to using Java with Spring MVC alone. This was especially true due to Ringo's support for hot deployment of code changes, and because our development team already had strong Javascript skills since the developers were previously responsible for end to end development encompassing not only the server side Spring code but also a Javascript heavy web application. Incorporating server side Javascript entailed a small learning curve for the team compared to incorporating an entirely new JVM language such as Groovy or Scala or Clojure, etc. Also compared to these other languages, our code was simplified owing to the ease of working with the RESTful JSON request and response payloads directly in RingoJS, where it's very easy to see the JSON payloads when reading our Javascript code. This contrasts with the other languages which of necessity must treat JSON as a "serialization" or "marshalling" format that must be converted into the other language's data structures and syntax for Groovy/Scala/Clojure/etc. As the team used RingoJS server side Javascript more, our coding style evolved into a more Functional style focused on simple data structures and pure functions in lieu of elaborate Object Oriented design patterns and class hierarchies. i.e. Our JSON request/response payloads were used directly as our "data structures" and they were passed in and out of Javascript functions organized into Ringo's CommonJS modules. So though Ringo allows you to call into Java easily (which we leveraged to call into our legacy Java code), we wrote our RingoJS server-side Javascript code in a simpler non-stateful/non-Object-Oriented style with less of the ceremony and verbosity that Java can bring.