rhoconnect 4.0.0.beta.10 → 4.0.0.beta.12

data/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 4.0.0.beta.12 (2013-04-26)
+* B-104783 - Add Node package dependency for Ubuntu/CentOS packages
+* B-91486 - Redis custom partitions
+* B-99049 - Implement 4.0 routes support in RhoConnect-Client
+* B-104736 - Additional JS API methods added:
+  * Store: getData, putData, getValue, putValue
+  * Model: stashResult, storeBlob, getData(md)
+* B-104738 - JS API documentation now available on edgedocs
+
+## 4.0.0.beta.11 (skipped for RMS version parity)
+
 ## 4.0.0.beta.10 (2013-04-18)
 * B-103674 - Add specs for testing blank rhoconnect app (run "rhoconnect" from any directory)
 * B-103671 - RhoConnect JavaScript support added

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    rhoconnect (4.0.0.beta.10)
+    rhoconnect (4.0.0.beta.12)
       bundler (~> 1.0)
       connection_pool (~> 1.0.0)
       json (~> 1.7.7)
@@ -50,7 +50,7 @@ GEM
       multi_json (~> 1.0)
     extlib (0.9.16)
     ffaker (1.14.0)
-    ffi (1.7.0)
+    ffi (1.8.1)
     fog (1.10.1)
       builder
       excon (~> 0.20)
@@ -84,7 +84,7 @@ GEM
       rainbow
       sprockets (~> 2)
     json (1.7.7)
-    mime-types (1.22)
+    mime-types (1.23)
     mono_logger (1.0.1)
     multi_json (1.7.2)
     nest (1.1.2)
@@ -104,7 +104,7 @@ GEM
       rack (>= 1.0)
     rainbow (1.1.4)
     rake (10.0.4)
-    redis (3.0.3)
+    redis (3.0.4)
     redis-namespace (1.2.1)
       redis (~> 3.0.0)
     resque (1.24.1)
@@ -140,7 +140,7 @@ GEM
       rack (~> 1.5, >= 1.5.2)
       rack-protection (~> 1.4)
       tilt (~> 1.3, >= 1.3.4)
-    sprockets (2.9.2)
+    sprockets (2.9.3)
       hike (~> 1.2)
       multi_json (~> 1.0)
       rack (~> 1.0)
@@ -156,7 +156,7 @@ GEM
       rack (>= 1.0.0)
     thor (0.15.4)
     tilt (1.3.7)
-    uuidtools (2.1.3)
+    uuidtools (2.1.4)
     vegas (0.1.11)
       rack (>= 1.0.0)
     webmock (1.9.3)

data/Rakefile

@@ -141,7 +141,7 @@ def build_pkg(dist, arch, deps)
   Dir.chdir("./pkg") # it created by build task and should already exist
 
   # Construct fpm command
-  fpm_cmd = "fpm -s dir -t #{dist} -n rhoconnect -v #{version} -a #{arch} -C #{build_dir} " +
+  fpm_cmd = "fpm -s dir -t #{dist} -n rhoconnect -v #{version} -a #{arch} -C #{build_dir} --epoch 1 " +
     "--before-install #{before_install_script} --after-install #{after_install_script} " +
     "--before-remove #{before_remove_script} --after-remove #{after_remove_script} " +
     "--prefix #{prefix} --description #{description}"

data/commands/generators/controller.rb

@@ -1,5 +1,5 @@
 Execute.define_task do
-  desc "source NAME", "Generate a new source adapter controller"
+  desc "source NAME", "Generate a new source adapter controller", :hide => true
   def controller(name,platform='ruby')
     Rhoconnect.run_cli(Dir.pwd, 'thorhoconnect', Rhoconnect::VERSION, ARGV)
   end #source

data/commands/generators/model.rb

@@ -1,5 +1,5 @@
 Execute.define_task do
-  desc "source NAME", "Generate a new source adapter model"
+  desc "source NAME", "Generate a new source adapter model", :hide => true
   def model(name,platform='ruby')
     Rhoconnect.run_cli(Dir.pwd, 'thorhoconnect', Rhoconnect::VERSION, ARGV)
   end #model

data/doc/deploying.txt

@@ -12,6 +12,8 @@ Every package provides the following components:
 
 * Ruby 1.9.3-p392
 
+* Node.js, version v0.10.4
+
 * Nginx HTTP server, release 1.3.x
 
 * Thin application server, release 1.5.x
@@ -31,8 +33,8 @@ Add the following line to the end of your <b>/etc/apt/sources.list</b>:
 
 	:::text
 	deb http://rhoconnect.s3.amazonaws.com/packages/deb rhoconnect main
-	
-**NOTE: If you want to get the package with cool new features from the Beta repository, then define 
+
+**NOTE: If you want to get the package with cool new features from the Beta repository, then define
 repo url as `http://rhoconnect.s3.amazonaws.com/beta-packages/deb`**
 
 Once the repo is added apt-get needs to be updated:
@@ -46,30 +48,31 @@ Once that is done, it is time to install RhoConnect:
 	$ sudo apt-get install rhoconnect
 
 #### Steps for RedHat-Based Linux Users
-Prerequisites: target Linux server should include CentOS Development tools. 
+Prerequisites: target Linux server should include CentOS Development tools.
 To install them, use the this command
 
- 	:::term	
+ 	:::term
 	$ yum groupinstall 'Development Tools'
-	
+
 It will install for you such tools as GNU GCC C/C++ compiler, make and others.
 
-Vanilla CentOS distribution does not include some packages required by RhoConnect installer. To resolve dependencies you 
+Vanilla CentOS distribution does not include some packages required by RhoConnect installer. To resolve dependencies you
 might wanted to use [Extra Packages for Enterprise Linux (EPEL) ](http://fedoraproject.org/wiki/EPEL)
-repository.
+repository and install Python26 out of it.
 
 For example, to enable EPEL repository for CentOS 5.x release execute these commands:
 
     :::term
-	$ wget http://mirror.us.leaseweb.net/epel/5/i386/epel-release-5-4.noarch.rpm
-	$ rpm -i epel-release-5-4.noarch.rpm
+  $ wget http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm
+	$ rpm -i epel-release-5*.rpm
 	$ yum update
+  $ yum install python26
 
 For CentOS 6.x release:
 
     :::term
-	$ wget http://ftp.osuosl.org/pub/fedora-epel/6/i386/epel-release-6-8.noarch.rpm
-	$ rpm -i epel-release-6-8.noarch.rpm
+  $ wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
+	$ rpm -i epel-release-6*.rpm
 	$ yum update
 
 Now you can create a file named <b>rhoconnect.repo</b> in the <b>/etc/yum.repos.d/</b> directory:
@@ -87,7 +90,7 @@ Copy and paste these contents into the file.
 	gpgcheck=0
 
 **NOTE: If you want to get the package with cool new features from the Beta repository, then define baseurl as
-`baseurl=http://rhoconnect.s3.amazonaws.com/beta-packages/rpm`** 
+`baseurl=http://rhoconnect.s3.amazonaws.com/beta-packages/rpm`**
 
 Once that is done, it is time to install RhoConnect:
 
@@ -234,7 +237,7 @@ f) As root user restart Thin, and Nginx servers
 
 **NOTE: Deploying multiple rhoconnect apps on nginx has not yet been tested. Perform these steps only if you are experienced with nginx.**
 
-To deploy and develop two rhoconnect applications on nginx and thin servers, 
+To deploy and develop two rhoconnect applications on nginx and thin servers,
 refer to the nginx documentation on [nginx server blocks](http://wiki.nginx.org/ServerBlockExample) to see how to configure an nginx sever for multiple host names.
 
 For each rhoconnect app, you need to set up its own redis instance. Refer to [the redis quick start documentation](http://redis.io/topics/quickstart).
@@ -253,16 +256,16 @@ or install required gems as `sudo /opt/rhoconnect/bin/gem install gem_name`**
 ## Nginx configuration for SSL with self-signed certificate
 
 ### About Self-Signed Certificates
-A SSL certificate is a way to encrypt a site's information and create a more secure connection. 
+A SSL certificate is a way to encrypt a site's information and create a more secure connection.
 This chapter will take you through generating a self-signed certificate to use with Nginx.
 
 ### Create a Directory for the Certificate
-The SSL certificate has 2 main parts: the certificate itself and the public key. To make all of the relevant files easy to access, you should create a directory to store them in: 
+The SSL certificate has 2 main parts: the certificate itself and the public key. To make all of the relevant files easy to access, you should create a directory to store them in:
 
 	:::term
 	$ sudo mkdir /opt/nginx/ssl
 
-We will perform the next few steps within the directory: 
+We will perform the next few steps within the directory:
 
 	:::term
 	$ cd /opt/nginx/ssl
@@ -272,21 +275,21 @@ We will perform the next few steps within the directory:
 Start by creating the private server key. During this process, you will be asked to enter a specific passphrase. Be sure to note this phrase carefully, if you forget it or lose it, you will not be able to access the certificate.
 
 	:::term
-	$ openssl genrsa -des3 -out server.key 1024  
+	$ openssl genrsa -des3 -out server.key 1024
 	Generating RSA private key, 1024 bit long modulus
 	..........++++++
 	..................++++++
 	e is 65537 (0x10001)
 	Enter pass phrase for server.key:
 	Verifying - Enter pass phrase for server.key:
-	
-Follow up by creating a certificate signing request: 
+
+Follow up by creating a certificate signing request:
 
 	:::term
 	$ openssl req -new -key server.key -out server.csr
 
-This command will prompt terminal to display a lists of fields that need to be filled in. 
-The most important line is "Common Name". Enter your official domain name here or, 
+This command will prompt terminal to display a lists of fields that need to be filled in.
+The most important line is "Common Name". Enter your official domain name here or,
 if you don't have one yet, your site's IP address. Leave the challenge password and optional company name blank.
 	:::term
 	Enter pass phrase for server.key:
@@ -308,8 +311,8 @@ if you don't have one yet, your site's IP address. Leave the challenge password
 	Please enter the following 'extra' attributes
 	to be sent with your certificate request
 	A challenge password []:
-	An optional company name []:	
-		
+	An optional company name []:
+
 ### Remove the Passphrase
 We are almost finished creating the certificate. However, it would serve us to remove the passphrase. Although having the passphrase in place does provide heightened security, the issue starts when one tries to reload nginx. In the event that nginx crashes or needs to reboot, you will always have to re-enter your passphrase to get your entire web server back online.
 
@@ -326,14 +329,14 @@ Keep in mind that you can specify how long the certificate should remain valid b
 	:::term
 	$ openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
 	Signature ok
-	subject= ... 
+	subject= ...
 	Getting Private key
 
 ### Set Up the Certificate
 Now we have all of the required components of the finished certificate.
 The next thing to do is to set up the virtual host to serve your domain from HTTS connection.
 
-Update existing Nginx `/opt/nginx/conf/conf.d/https_rhoconnect.conf` configuration file by including the newly signed certificate and private key: 
+Update existing Nginx `/opt/nginx/conf/conf.d/https_rhoconnect.conf` configuration file by including the newly signed certificate and private key:
 	:::term
 	upstream thin_cluster {
 	  # ...
@@ -352,12 +355,12 @@ Update existing Nginx `/opt/nginx/conf/conf.d/https_rhoconnect.conf` configurati
 
 	        ssl on;
 	        ssl_certificate /opt/nginx/ssl/server.crt;
-	        ssl_certificate_key /opt/nginx/ssl/server.key; 
+	        ssl_certificate_key /opt/nginx/ssl/server.key;
 	}
-	
+
 
 ### Activate the Virtual Host
-Restart nginx: 
+Restart nginx:
 	:::term
 	$ /etc/init.d/nginx restart
 
@@ -425,7 +428,7 @@ You can start a redis server using the following command.
 	$ sudo /etc/init.d/redis start
 
 ### RhoConnect Push Service
-You can create a RhoConnect Push production environment on Linux servers by installing prepackaged software for 
+You can create a RhoConnect Push production environment on Linux servers by installing prepackaged software for
 Ubuntu (12.x) and CentOS (5.x/6.x). In a few clicks, you will have installed on your Linux server.
 
 * Node.js with Npm package manager
@@ -457,8 +460,8 @@ Node.js requires python 2.6 which is not available for CentOS 5 stock version.
 For this flavor of linux you need to manually install EPEL repo and install python26 RPM out of it:
 
 	:::term
-    $ wget http://mirror.chpc.utah.edu/pub/epel/5/i386/epel-release-5-4.noarch.rpm
-    $ rpm -i epel-release-5-4.noarch.rpm 
+    $ wget http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm
+    $ rpm -i epel-release-5*.rpm
     $ yum install python26
 
 
@@ -489,9 +492,9 @@ and deploy it into the J2EE App Server.
 Deploying the WAR container varies per J2EE App Server, for JBoss it is necessary
 to place the WAR file into the server's deploy directory.
 
-#### Deploying warbler package on Apache Tomcat web server 
-To successfully deploy warbler package on Tomcat you need to make rhoconnect app be the default app. There are a few ways to reach 
-this goal and we describe only a couple of them. 
+#### Deploying warbler package on Apache Tomcat web server
+To successfully deploy warbler package on Tomcat you need to make rhoconnect app be the default app. There are a few ways to reach
+this goal and we describe only a couple of them.
 
 ##### Method 1
 
@@ -504,7 +507,7 @@ this goal and we describe only a couple of them.
 4) Drop the `ROOT.war` file directly in the `$CATALINA_BASE/webapps` directory
 
 5) Start Tomcat `startup.sh`
-  
+
 ##### Method 2
 
 1) Stop Tomcat
@@ -514,7 +517,7 @@ this goal and we describe only a couple of them.
 3) Turn off autoDeploy and deployOnStartup in your Host element in the server.xml file.
 
 4) Explicitly define your application context in server.xml, specifying both path (must be empty!) and docBase.
-    
+
 	:::xml
 	<Host name="localhost"  appBase="webapps"
 		 unpackWARs="true" autoDeploy="false" deployOnStartup="false">
@@ -523,8 +526,8 @@ this goal and we describe only a couple of them.
 		 <!-- ...  -->
 	</Host>
 
-5) Start Tomcat	
-	
+5) Start Tomcat
+
 ## Deploying on Heroku
 
 #### Prerequisites

data/doc/source-adapters-js.txt

@@ -0,0 +1,263 @@
+RhoConnect Source Adapters (JavaScript)
+===
+
+## Generating the Source Adapter from the Command Line
+
+To generate a JavaScript source adapter for your RhoConnect application, you can run the `rhoconnect source --js` command within your application directory.
+
+    :::term
+    $ rhoconnect source --help
+    Usage: rhoconnect source [options] [args]
+
+    Generates a new source adapter (Controller/Model pair).
+    Required:
+      name        - source name (i.e. product)
+
+
+    Options specific for this generator:
+            --js                         generate JavaScript code
+
+    General options:
+        -p, --pretend                    Run, but do not make any changes.
+        -f, --force                      Overwrite files that already exist.
+        -s, --skip                       Skip files that already exist.
+        -d, --delete                     Delete files that have previously been generated with this generator.
+            --no-color                   Don't colorize the output
+        -h, --help                       Show this message
+            --debug                      Do not catch errors
+
+
+For the storeserver application example, within the storeserver directory, run:
+
+    :::term
+    $ rhoconnect source product --js
+    Generating with source generator:
+         [ADDED]  models/js/product.js
+         [ADDED]  controllers/js/product_controller.js
+
+
+## Understanding the Generated Controller File
+
+The generated source adapter's controller file (in this case, `controllers/product_controller.js`) is similar to the code listing below.
+Its purpose is to define the RhoConnect application HTTP end point and to register the corresponding SYNC routes.
+
+    :::javascript
+    var app = require("ballroom");
+    var helpers = require("rhoconnect_helpers");
+
+    app.controllerName("Product");
+    app.registerHandler("sync");
+
+    // Add your custom routes here
+
+## Understanding the Generated Model File
+
+The generated source adapter's model file (in this case, `models/product.js`) is similar to the code listing below:
+
+    :::javascript
+    var Product = function(){
+
+      this.login = function(resp){
+        // TODO: Login to your data source here if necessary
+        resp.send(true);
+      };
+
+      this.query = function(resp){
+        var result = {};
+        // TODO: Query your backend data source and assign the records
+        // to a nested hash structure. Then return your result.
+        // For example:
+        //
+        // {
+        //   "1": {"name": "Acme", "industry": "Electronics"},
+        //   "2": {"name": "Best", "industry": "Software"}
+        // }
+        resp.send(result);
+      };
+
+      this.create = function(resp){
+        // TODO: Create a new record in your backend data source.  Then
+        // return the result.
+        resp.send('someId');
+      };
+
+      this.update = function(resp){
+        // TODO: Update an existing record in your backend data source.
+        // Then return the result.
+        resp.send(true);
+      };
+
+      this.del = function(resp){
+        // TODO: Delete an existing record in your backend data source
+        // if applicable.  Be sure to have a hash key and value for
+        // "object" and return the result.
+        resp.send(true);
+      };
+
+      this.logoff = function(resp){
+        // TODO: Logout from the data source if necessary.
+        resp.send(true);
+      };
+    };
+
+    module.exports = new Product();
+
+## Source Adapter API
+
+### Source Adapter Controller API
+
+You can use the following methods and techniques inside of your source adapter controller.
+
+* [controllerName](/rhoconnectapi/source-adapter-controller-api-js#controllernamename) - Name of the source adapter controller.
+* [registerHandler](/rhoconnectapi/source-adapter-controller-api-js#registerhandlername) - Register a RhoConnect handler for the controller.
+* [get](/rhoconnectapi/source-adapter-controller-api-js#getroute-options-callback) - Define a GET route.
+* [post](/rhoconnectapi/source-adapter-controller-api-js#postroute-options-callback) - Define a POST route.
+* [put](/rhoconnectapi/source-adapter-controller-api-js#putroute-options-callback) - Define a PUT route.
+* [del](/rhoconnectapi/source-adapter-controller-api-js#delroute-options-callback) - Define a DELETE route.
+* [currentUser](/rhoconnectapi/source-adapter-model-api-js#currentuser) - Returns the current user who called the adapter's model.
+* [loadModel](http://localhost:9393/rhoconnectapi/source-adapter-controller-api-js#loadmodelname) - Returns the current model instance for this controller.
+
+### Source Adapter Model API
+
+You can write the following methods for your source adapter model. These methods will be called by the controller at run-time and allow your source adapter model to interact with your backend service.
+
+* [login](/rhoconnectapi/source-adapter-model-api-js#login) - Login to your backend service.
+* [logoff](/rhoconnectapi/source-adapter-model-api-js#logoff) - Logoff from your backend service.
+* [query](/rhoconnectapi/source-adapter-model-api-js#query) - Query your backend service and build a hash of hashes.
+* [create](/rhoconnectapi/source-adapter-model-api-js#create) - Create a new record in the backend.
+* [update](/rhoconnectapi/source-adapter-model-api-js#update) - Update an existing record in the backend.
+* [del](/rhoconnectapi/source-adapter-model-api-js#del) - Delete an existing record in the backend.
+* [stashResult](/rhoconnectapi/source-adapter-model-api-js#stashresultresp) - Saves the current state of the result to redis and sets it `undefined`.
+* [getData](/rhoconnectapi/source-adapter-model-api-js#getdataresp-callback) - Get the model document data from Store.
+* [currentUser](/rhoconnectapi/source-adapter-model-api-js#currentuser) - Returns the current user who called the adapter's model.
+* [storeBlob](/rhoconnectapi/source-adapter-model-api-js#storeblob) - Save the incoming blob data into permanent storage for the future processing.
+
+
+### Request API
+The [request object](/rhoconnectapi/source-adapter-request-api-js) contains information about the HTTP request the app is receiving.
+
+* [params](/rhoconnectapi/source-adapter-request-api-js#params) - Access in the incoming request parameters (i.e. from the HTTP query string).
+* [header](/rhoconnectapi/source-adapter-request-api-js#header) - HTTP request headers.
+* [model](/rhoconnectapi/source-adapter-request-api-js#model) - The corresponding model name of the request.
+
+### Response API
+The [response](/rhoconnectapi/source-adapter-response-api-js) is used to pass application control and return the `result` hash to RhoConnect.
+
+* [params](/rhoconnectapi/source-adapter-response-api-js#params) - Access in the incoming request parameters (i.e. from the HTTP query string).
+* [header](/rhoconnectapi/source-adapter-response-api-js#header) - HTTP request headers.
+* [send](/rhoconnectapi/source-adapter-response-api-js#sendvalue) - Return program control (most controller and model methods will need to do this).
+* [exception](/rhoconnectapi/source-adapter-response-api-js#exception) - Holds the exception for the request (if one is raised).
+* [currentUser](/rhoconnectapi/source-adapter-model-api-js#currentuser) - Returns the current user who called the adapter's model.
+
+## Store API
+RhoConnect provides a simple [redis interface](/rhoconnectapi/source-adapter-store-api-js) for saving/retrieving arbitrary data.  This is useful if you want to save data in your application to be used later (i.e. in an async job or a subsequent source adapter execution).
+
+* [getValue](/rhoconnectapi/source-adapter-store-api-js#getvaluerespcallback) - Retrieve a simple value from redis.
+* [putValue](/rhoconnectapi/source-adapter-store-api-js#putvaluerespcallback) - Add a simple value to redis.
+* [getData](/rhoconnectapi/source-adapter-store-api-js#getdatarespcallback) - Retrieve an array or hash from redis.
+* [putData](/rhoconnectapi/source-adapter-store-api-js#putdatarespcallback) - Add an array or hash to redis.
+
+## Sample Model
+Here's a complete example of how the completed [product model might look](https://gist.github.com/larsburgess/87753882f3a4a366b48b):
+
+    :::javascript
+    var http = require('http');
+    var host = 'rhostore.herokuapp.com';
+
+    var Product = function(){
+
+      this.login = function(resp){
+        resp.send(true);
+      };
+
+      this.query = function(resp){
+        var result = {};
+        var str = '';
+
+        http.request('http://' + host + '/products.json', function(res){
+          res.on('data', function(chunk){
+            str += chunk;
+          });
+          res.on('end', function(){
+            var data = JSON.parse(str);
+            for(var i in data){
+              var item = data[i];
+              result[item.product.id.toString()] = item.product;
+            }
+            resp.send(result);
+          });
+        }).end();
+      };
+
+      this.create = function(resp){
+        var postData = JSON.stringify({ 'product': resp.params.create_object });
+        var str = '';
+        var options = {
+          host: host,
+          path: '/products.json',
+          method: 'POST',
+          headers: { 'Content-Type': 'application/json' }
+        };
+        var req = http.request(options, function(res){
+          res.on('data', function(chunk){
+            str += chunk;
+          });
+          res.on('end', function(){
+            var data = JSON.parse(str);
+            resp.send(data.product.id.toString());
+          });
+        });
+        req.write(postData);
+        req.end();
+      };
+
+      this.update = function(resp){
+        var objId = resp.params.update_object.id;
+        var putData = JSON.stringify({ "product": resp.params.update_object });
+        // Remove the id from the hash, we don't need it.
+        delete putData.id;
+        var options = {
+          host: host,
+          path: '/products/' + objId + '.json',
+          method: 'PUT',
+          headers: { 'Content-Type': 'application/json' }
+        };
+        var req = http.request(options, function(res){
+          res.on('data', function(){});
+          res.on('end', function(){
+            resp.send(true);
+          });
+          res.on('error', function(){
+            resp.send(false);
+          });
+        });
+        req.write(putData);
+        req.end();
+      };
+
+      this.del = function(resp){
+        var objId = resp.params.delete_object.id;
+        var options = {
+          host: host,
+          path: '/products/' + objId + '.json',
+          method: 'DELETE',
+          headers: { 'Content-Type': 'application/json' }
+        };
+        var req = http.request(options, function(res){
+          res.on('data', function(){});
+          res.on('end', function(){
+            resp.send(true);
+          });
+          res.on('error', function(){
+            resp.send(false);
+          });
+        });
+        req.end();
+      };
+
+      this.logoff = function(resp){
+        resp.send(true);
+      };
+    };
+
+    module.exports = new Product();

data/generators/templates/application/controllers/js/application_controller.js

@@ -1,13 +1,15 @@
-var app = require("ballroom");
-app.controllerName("Application");
+var app = require('ballroom');
+var rc = require('rhoconnect_helpers');
+app.controllerName('Application');
 
-app.post("/login",{"rc_handler":"authenticate"}, function(req,resp){
+app.post('/login',{'rc_handler':'authenticate',
+  'deprecated_route': {'verb': 'post', 'url': ['/application/clientlogin']}}, function(req,resp){
   var login = req.params.login;
   var password = req.params.password;
   resp.send(true);
 });
 
-app.get("/rps_login",{"rc_handler":"rps_authenticate"}, function(req,resp){
+app.get('/rps_login',{'rc_handler':'rps_authenticate'}, function(req,resp){
   var login = req.params.login;
   var password = req.params.password;
   resp.send(true);

data/generators/templates/source/controllers/js/controller.js

@@ -1,7 +1,7 @@
-var app = require("ballroom");
-var helpers = require("rhoconnect_helpers");
+var app = require('ballroom');
+var rc = require('rhoconnect_helpers');
 
-app.controllerName("<%=class_name%>");
-app.registerHandler("sync");
+app.controllerName('<%=class_name%>');
+app.registerHandler('sync');
 
 // Add your custom routes here

data/generators/templates/source/models/js/model.js

@@ -1,4 +1,6 @@
-var <%=class_name%> = function() {
+var rc = require('rhoconnect_helpers');
+
+var <%=class_name%> = function(){
 
   this.login = function(resp){
     // TODO: Login to your data source here if necessary