Angular service to Stomp Websocket Library. This library is an interface between native Stomp comunication and AngularJS This service relies on stomp.js that can be found at: https://github.com/jmesnil/stomp-websocket/
This library is developped in ES2015 (and with some ES20XX features) and transpilled into plain old Javascript for browser compatibility. You can choose to use this lib from a standard AngularJS Project or inside a AngularJS written in ES2015.
You have to import the transpiled files (normaly located in the dist folder) in your Single Page App. Don't forget to import Angular and Stomp.js first (because the lib relies on it).
<script src="js/lib/stompjs/stomp.js" />
<script src="js/lib/AngularStompDK/angular/angular.min.js" />
<script src="js/lib/AngularStompDK/dist/angular-stomp.min.js" />And add the dependency to your Angular application :
angular.module('myApp', [ 'AngularStompDK' ])You can install this package with the standard node package manager, with a simple npm install AngularStompDK
You can now (since version 0.4.0) import AngularStompDK directly from JSPM (Package manager build upon SystemJS)
$ jspm install github:AngularStompDK
All the dependencies will automatically be fetch (kind of magic, isn't it :D) and you just have to register the lib at the AngularJS level (described here with the bootstrap method, commonly used in JSPM | ES2015 environnement).
import angular from 'angular';
import 'AngularStompDK'; // <-- Loading the full transpiled file from dist
...
let app = angular.module('MyWonderfullStompApp', [ 'AngularStompDK' ] );
angular
.element(document)
.ready(() => angular.bootstrap(element, [ app ] ));You also can load the ES2015 file and use your current transpiler to use AngularStompDK. For this, we have to use the relative path of the entrypoint in the project
import angular from 'angular';
import ngStomp from 'AngularStompDK/core/ngStomp'; // Path to the main ES6 Module
...
let app = angular.module('MyWonderfullStompApp', [ ngStomp.name ] );
... All the code example will be written in ES5 for the moment, if some of you would like to have example in ES2015, open an issue or do a PR.
Configure the ngStomp module to connect to your web-socket system :
angular.module('myApp')
.config(function(ngstompProvider){
ngstompProvider
.url('/ws')
.credential('login', 'password')
});If you want to use a sub-system to do the connection, like SockJS, you can add the class name in the configuration part. Don't forget to import this underlying library in your page via Bower (and HTML script tag or other) or via JSPM.
angular.module('myApp')
.config(function(ngstompProvider){
ngstompProvider
.url('/ws')
.credential('login', 'password')
.class(SockJS); // <-- Will be used by StompJS to do the connection
});Use it inside your controller (or everywhere you want !)
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.connect()
function whatToDoWhenMessageComming(message) {
items.push(JSON.parse(message.body));
}
});You can chain multiple subscribe and add headers to your subscription :
angular.controller('myController', function($scope, ngstomp) {
var vm = this, headers = {
foo : 'bar'
};
vm.items = [];
ngstomp
.subscribeTo('/topic/item1')
.callback(whatToDoWhenMessageComming)
.and()
.subscribeTo('/topic/item2')
.callback(whatToDoWhenMessageComming)
.withHeaders(headers)
.connect();
function whatToDoWhenMessageComming(message) {
vm.items.push(JSON.parse(message.body));
}
});If the body has to be in JSON, let the library handle the transformation of message.body
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.withBodyInJson()
.connect();
function whatToDoWhenMessageComming(message) {
items.push(message.body);
}
});Since 0.9.0 : You also can disable the digest cycle to be performed after each reception (enabled by default)
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.withBodyInJson()
.withDigest(false)
.connect();
function whatToDoWhenMessageComming(message) {
items.push(message.body);
}
});Give to the builder the $scope to allow the system to un-register the connection after the $scope destruction :
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.withBodyInJson()
.bindTo($scope)
.connect();
function whatToDoWhenMessageComming(message) {
items.push(message.body);
}
});Or, in an angular component environment, use the $onDestroy hook to un-register the connection, and thanks to this, you should not need to use the old and ugly $scope :
angular.component('myComp', {
bindings : {},
controller : function(ngstomp) {
this.$onInit = function() {
this.items = [];
this.unSubscriber = ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.withBodyInJson()
.bindTo($scope)
.connect();
};
this.$onDestroy = function() {
this.unSubscriber.unSubscribeAll();
}
this.whatToDoWhenMessageComming = function(message) {
items.push(message.body);
}
}
});You can send back information to the Web-Socket :
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.bindTo($scope)
.connect();
function whatToDoWhenMessageComming(message) {
items.push(JSON.parse(message.body));
}
var objectToSend = { message : 'Hello Web-Socket'},
stompHeaders = {headers1 : 'xx', headers2 : 'yy'};
this.sendDataToWS = function(message) {
ngstomp
.send('/topic/item/message', objectToSend, stompHeaders);
}
});When you send data, the system return a promise (like in standard rest communication :D), so you can chain multiple synchronous communication :
angular.controller('myController', function($scope, ngstomp) {
var items = [];
ngstomp
.subscribeTo('/topic/item')
.callback(whatToDoWhenMessageComming)
.bindTo($scope)
.connect();
function whatToDoWhenMessageComming(message) {
items.push(JSON.parse(message.body));
}
var objectToSend = { message : 'Hello Web-Socket'},
stompHeaders = {headers1 : 'xx', headers2 : 'yy'};
this.sendDataToWS = function(message) {
ngstomp
.send('/topic/item/message1', objectToSend, stompHeaders)
.then(function() { return ngstom.send('/topic/item/message2', objectToSend, stompHeaders) });
.then(function() { return ngstom.send('/topic/item/message3', objectToSend, stompHeaders) });
}
});The connect() function return an object commonly called an unSubscriber. It handles all the logic of unSubscribing from a Stomp topic.
You can, for example, unSubscribed from all the subject at once with the function unSubscribeAll():
angular.controller('myController', function(ngstomp) {
var vm = this;
var unSubscriber = ngstomp
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1)
.and()
.subscribeTo('/topic/item2')
.callback(receiveFromTopic2)
.connect();
function receiveFromTopic1(m) { vm.items.push(JSON.parse(m.body)); }
function receiveFromTopic2(m) { vm.items.push(JSON.parse(m.body)); }
vm.unSubscribeAll = function() {
unSubscriber.unSubscribeAll();
}
});Or you can choose to unSubscribed a subject by its topic url with the function unSubscribeOf(TOPIC_URL):
angular.controller('myController', function(ngstomp) {
var vm = this;
var unSubscriber = ngstomp
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1)
.and()
.subscribeTo('/topic/item2')
.callback(receiveFromTopic2)
.connect();
function receiveFromTopic1(m) { vm.items.push(JSON.parse(m.body)); }
function receiveFromTopic2(m) { vm.items.push(JSON.parse(m.body)); }
vm.unSubOfTopic1 = function() {
unSubscriber.unSubscribeOf('/topic/item1');
}
vm.unSubOfTopic2 = function() {
unSubscriber.unSubscribeOf('/topic/item2');
}
});Because you can register the same topic with different parameters (callback, headers...), the function unSubscribeOf(TOPIC_URL) will unsubscribe from any topic with the same url, so it coul lead to multiple unsubscribe.
If you want to unsubscribe from 1 topic specificaly, you have two solution :
First one, without doing chaining in subscription :
angular.controller('myController', function(ngstomp) {
var vm = this;
var unSubscriberFirst = ngstomp
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1)
.connect();
var unSubscriberSecond = ngstomp
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1WithDifferentAction)
.withHeaders({foo : 'bar'})
.connect();
function receiveFromTopic1(m) { vm.items.push(JSON.parse(m.body)); }
function receiveFromTopic1WithDifferentAction(m) { console.log(JSON.parse(m.body)); }
vm.unSubOfFirst = function() {
unSubscriberFirst.unSubscribeAll();
}
vm.unSubOfSecond = function() {
unSubscriberSecond.unSubscribeAll();
}
});The previous version is too verbose and lead to multiple var declaration. You can use the function unSubscribeNth(Nth_Subscription) on the unSubscriber.
The nth position is '0 based', so the first is 0 (like in an array :D).
angular.controller('myController', function(ngstomp) {
var vm = this;
var unSubscriberFirst = ngstomp
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1)
.and()
.subscribeTo('/topic/item1')
.callback(receiveFromTopic1WithDifferentAction)
.withHeaders({foo : 'bar'})
.connect();
function receiveFromTopic1(m) { vm.items.push(JSON.parse(m.body)); }
function receiveFromTopic1WithDifferentAction(m) { console.log(JSON.parse(m.body)); }
vm.unSubOfFirst = function() {
unSubscriberFirst.unSubscribeNth(1);
}
vm.unSubOfSecond = function() {
unSubscriberSecond.unSubscribeNth(2);
}
});The $scope is the only bridge between Angular Lifecycle and standard HTML behaviour (like web-socket). To keep both in sync, we have to use the $scope.
This project is totally open-source, and I'll be glad to see Push Request, so Fork it, improve it, test it (don't forget !) and do PR. It's very simple to work that way.
First of all, I encourage you to read the implementation of the lib, and even the tests. Right now, it's only 200 lines of code (without the test), so it's very simple (read the ES2015 version, not the transpilled version...). If it doesn't help, feel free to open a issue on the github, and if I can help, I will try to.
Like the previous question, open an issue and I will add it to this README (or you can do a PR only on this file).