Making a AngularJS based Liferay portlet instanceable

In one of my previous posts I showed how to create a Liferay portlet based on AngularJS. The problem with that concept was, that only a single portlet of that kind could be placed on a portal page.
I will show now how to improve the concept to not only allow multiple AngularJS portlets on a single Liferay page, but to allow the same portlet multiple times on a page.

The key is to manually bootstrap the AngularJS apps on the page, so we can no longer simple use ng-app. Instead of:

  <div ng-app>

We assign an ID to our root DIV und attach the AngularJS module to it:

<div id="angularjsPortletDemo">

<script type="application/javascript" th:inline="javascript">
  (function() {
    if (typeof(AUI) !== 'undefined') {
      /* We are within Liferay */
      AUI().ready(function() {
    } else {
      document.addEventListener("DOMContentLoaded", function(event) {

    function startAngular() {
      var appRootElem = document.getElementById('angularjsPortletDemo');
      angular.bootstrap(appRootElem, ['angularjsPortletDemo']);

To make the portlet acutally instanceable we have to do more:

  1. Get rid of the global JavaScript variables in the HEAD (which we used to pass parameters from the backend such as the AJAX URL).
  2. Replace the ID on the root DIV by the actual Liferay portlet ID
  3. Change the Liferay portlet configuration

For the first step we just move the global variables into the IIFE block where the AngularJS bootstrapping happens. And we pass the variables to AngularJS as values to be able to use it in the AngularJS dependency injection system:

function startAngular() {
    var ajaxURL = /*[[${ajaxURL}]]*/ "/testdata/";
    var isStandalone = /*[[${standalone}]]*/ true;
    var authenticatedUser = /*[[${authenticatedUser}]]*/ "anonymous";

    var app = angular.module('angularjsPortletDemo');
    app.value('ajaxUrl', ajaxURL);
    app.value('isStandalone', isStandalone);
    app.value('authenticatedUser', authenticatedUser);

    var appRootElem = document.getElementById('angularjsPortletDemo');
    angular.bootstrap(appRootElem, ['angularjsPortletDemo']);

For the second step we use Thymeleaf to inject the portletId into the HTML template:

public String view(RenderRequest request, RenderResponse response, ModelMap model) {
  ThemeDisplay themeDisplay = (ThemeDisplay) request.getAttribute(WebKeys.THEME_DISPLAY);
  PortletDisplay portletDisplay = themeDisplay.getPortletDisplay();
  model.addAttribute("portletId", portletDisplay.getId());
<div id="angularjsPortletDemo" th:id="${portletId}" 


var portletId = /*[[${portletId}]]*/ 'angularjsPortletDemo';

var appRootElem = document.getElementById(portletId);
angular.bootstrap(appRootElem, ['angularjsPortletDemo']);

The last and most simple step to make the portlet instantiable is to set the homonymous attribute in liferay-portlet.xml:


And the best of all: The AngularJS app can still be launched standalone: Just run grunt server on the console!

The full code can be found on GitHub.

Creating a Liferay portlet based on AngularJS

After my post about converting an existing AngularJS app into a portlet I’ve got a lot of requests about how to integrate the portlet with the portal backend.
So I’ve created a little demonstrator and put in on GitHub: It uses Spring Portlet MVC and thymeleaf as template engine as backend.

Communication to the backend

The AJAX communication with the backend is based on resource requests which are originally intended to serve static resources such as images and JavaScript (see:

To pass the resource URL (which is generated and quite complicated) to the AngularJS app the demonstrator uses thymeleaf’s Script Inlining support. Within the head section of index.html:

<script type="text/javascript" th:inline="javascript">
  var angularJsPortletAjaxURL = /*[[${ajaxURL}]]*/ "/testdata/";
  var angularJsPortletStandalone = /*[[${standalone}]]*/ true;
  var angularJsPortletAuthenticatedUser = /*[[${authenticatedUser}]]*/ "anonymous";

And within the controller method responsible for the View phase:

public String view(RenderRequest request, RenderResponse response, ModelMap model) {
  User user = (User) request.getAttribute(WebKeys.USER);
  String userScreenName = user != null ? user.getScreenName() : "anonymous";

  ResourceURL baseResourceUrl = response.createResourceURL();

  model.addAttribute("ajaxURL", baseResourceUrl.toString());
  model.addAttribute("standalone", false);
  model.addAttribute("authenticatedUser", userScreenName);

  return "index";

To invoke a specifc controller method and fetch some data a POST request is sent to the resource URL extended by the resource id (&p_p_resource_id={myResourceId}).
The code within AngularJS looks like this:

var method = 'users';
var params = { "startIndex": startIndex, "limit": limit };

  url: angularJsPortletAjaxURL + "&p_p_resource_id=" + method,
  method: 'POST',
  params: params
.success(function(data) { 
/* ... */ 

And the AJAX call will invoke the controller method with the corresponding ResourceMapping annotation:

public void users(@RequestParam int startIndex, 
  @RequestParam int limit, ResourceResponse response) throws Exception {
    UserList users = /* fetch the users */


    //Automatic JSON serialization doesn't work yet in Protlet MVC
      response.getPortletOutputStream(), users);

Javascript and CSS resources

The JavaScript and CSS resources are not directly added to the HTML, but rather declared in liferay-portlet.xml like this:

  <!-- ... --> 

Standalone Mode

A very interesting opportunity when developing a HTML5 portlet is that you can run it standalone. This greatly accelerates the development. Since thymeleaf templates are pure HTML it’s no big deal at all.

In the demonstrator I’ve added the JavaScript and CSS resources, which are normally added by the portal, to the HTML (index.html) too. But only in the case the app runs in standalone mode. If the standalone property is set within the portlet controller the script tag is not rendered:

 <script type="application/javascript" src="js/app.js" 

Secondly I’ve created a test backend which delivers test data (JSON) when the portal is not available. There actual implementation is selected based on the global angularJsPortletStandalone variable which will also be rewritten by thymeleaf:

.factory('backend', function($http) {
  var portletBackend = /* ... */;

  var testBackend = /* ... */;

  if (angularJsPortletStandalone) {
    return testBackend;
  } else {
    return portletBackend;

The test backend also comes in handy when you use Jasmine to unit test your JavaScript code (something you should definitely consider).

I hope the demo portlet is helpful. Don’t hesitate to post remarks and comments.

Bringing the Java and Javascript world together

Many companies with Java as primary platform nowadays start to write pure HTML5/JavaScript front-ends, which is basically a good idea, since most Java Web Frameworks are quite painful.

The question is, how to integrate such an App into the existing Maven/Graddle build and how to deploy it on the application server. Since JavaScript has its own ecosystem of build and packaging systems, such as Node.js, Grunt or Bower.

One approach, I see a lot, is to integrate HTML5/JavaScript completely into the Java Project structure and let Maven trigger the JavaScript build. The idea is to just put all the JavaScript code and assets into a Maven WAR module and use the grunt-maven-plugin, or something similar, to launch the Grunt build.

Well, that works, but I’d advice against this approach, because:

  • It’s odd to couple two full featured build systems
  • Their build phases are not synchronized: The whole Grunt build, including the JavaScript tests, is executed in the Maven Test phase (default)
  • It slows things up to launch Maven and the Java VM to just start-up V8 and Grunt
  • The developers will start to use the Java Application Server instead of node.js for development, which is significantly slower and doesn’t allowed to run jshint and the JavaScript unit tests in the background
  • As your JavaScript applications grow you might want to re-use some Code and CSS in other Apps. That’s not possible with the integrated approach.
  • You might hire some JavaScript hackers which are not pretty familiar with the Java tooling landscape.

I present here an approach, which builds the Java and JavaScript stuff separately and merges it together at the end. The steps are:

  1. On the JavaScript side:
    1. Create separated HTML5/JavaScript modules with Grunt and Bower as build and packaging system
    2. Use a Grunt compress task to create Bower compatible ZIP file as the last build step
    3. Use a custom Grunt task to generate a Maven POM file, which just includes a build-helper:attach-artifact goal to turn the Bower ZIP file into a Maven artifact
    4. Add the project as dependency to another Bower module by just stating the full URL to the generated ZIP file. Which could of course be an URL of a Nexus or Artifactory repository.
  2. On the Build Server:
    1. On your build server run mvn install in the folder of the generated POM to install the Bower ZIP as Maven artifact in your local repository
    2. Install the artifact on Nexus or Artifactory
  3. On the Java side:
    1. Add the ZIP as dependency and unpack it into your WAR module in the package phase

Create the HTML5/JavaScript projects

To make things a bit more interesting we’re going to creating two Bower modules: A Theme, with just a single CSS file, and a AngularJS App.

The Theme project contains just a css/theme.css and a bower.json configuration like this:

  "name": "myTheme",
  "version": "1.0.0-SNAPSHOT",
  "main": "theme.css",
  "dependencies": {
    "bootstrap": "~3.1"

In package.json we need to add grunt-contrib-compress as a development dependency:

  "dependencies": {
  "devDependencies": {
    "grunt": "~0.4.1",
    "bower": "~1.3",
    "grunt-contrib-cssmin": "~0.7.0",
    "grunt-contrib-compress": "~0.7.0"
  "scripts": {
    "postinstall": "bower install"
  "engines": {
    "node": ">=0.8.0"

In Gruntfile.js we have to add a compress task and a custom task to generate a pom.xml:

module.exports = function (grunt) {
   cssmin: {
    combine: {
    files: {
      'dist/theme.css': ['css/theme.css']
  compress: {
    main: {
     options: {
       archive: 'deploy/'
      files: [
        { expand: true, cwd: 'dist/', src: ['**'], dest: '/'},
        { src: ['bower.json'], dest: '/'}
  grunt.registerTask('mavenpom', function () {
   var bowerJson = grunt.file.readJSON('bower.json');
   grunt.log.writeln('Determined project version: ' + bowerJson.version);
   var pom = '<?xml version="1.0" encoding="UTF-8"?>\n' +
     '<project xmlns=""' +
     ' xmlns:xsi=""' +
     ' xsi:schemaLocation="">\n' +
     '  <modelVersion>4.0.0</modelVersion>\n' +
     '  <groupId>at.nonblocking.bower</groupId>\n' +
     '  <artifactId>myTheme</artifactId>\n' +
     '  <packaging>pom</packaging>\n' +
     '  <version>' + bowerJson.version + '</version>\n' +
     '  <build>\n' +
     '    <plugins>\n' +
     '      <plugin>\n' +
     '        <groupId>org.codehaus.mojo</groupId>\n' +
     '        <artifactId>build-helper-maven-plugin</artifactId>\n' +
     '        <version>1.8</version>\n' +
     '        <executions>\n' +
     '          <execution>\n' +
     '            <id>attach-artifacts</id>\n' +
     '            <phase>package</phase>\n' +
     '            <goals>\n' +
     '              <goal>attach-artifact</goal>\n' +
     '            </goals>\n' +
     '            <configuration>\n' +
     '              <artifacts>\n' +
     '                <artifact>\n' +
     '                  <file>deploy/</file>\n' +
     '                   <type>zip</type>\n' +
     '                </artifact>\n' +
     '              </artifacts>\n' +
     '            </configuration>\n' +
     '          </execution>\n' +
     '        </executions>\n' +
     '      </plugin>\n' +
     '    </plugins>\n' +
     '  </build>\n' +
     '</project> ';
   grunt.log.writeln('Writing deploy/pom.xml');
   grunt.file.write('deploy/pom.xml', pom);
  grunt.registerTask('default', [

Please note, the POM artifactId and version is taken from bower.json!

If we now execute:

npm install
cd deploy
mvn install

a Bower module is generated and installed it as Maven artifact.

For the actual app we can use Yeoman to generate a AngularJS hello world example:

npm install -g yo
npm install -g generator-angular  
yo angular

And should get a structure like this:


Let’s say, the myTheme project is already on an artifactory repository, then you can add it as dependency like this:

  "name": "myApp",
  "version": "1.0.0-SNAPSHOT",
  "dependencies": {
    "angular": "1.2.16",
    "angular-resource": "1.2.16",
    "angular-cookies": "1.2.16",
    "angular-sanitize": "1.2.16",
    "angular-route": "1.2.16"
    "myTheme": "http://myserver/artifactory/release/at/nonblocking/bower/myTheme-1.0.0-SNAPSHOT/"

Furthermore you have to add the same compress and mavenpom task to Gruntfile.js as for the myTheme module.

Create the Jenkins Jobs

On Jenkins we will need two jobs to build myTheme and myApp. Just create two free-style projects, configure the source code management section accordingly and add node.js to the PATH:


Then create two build tasks for each job:

  1. An Execute Shell build step to start the grunt default task
  2. And a Maven step to install the generated bower ZIP locally in your repository


The last step on Jenkins is to publish the ZIP artifact in your remote repository:

Create the Java WAR module

The configuration of the WAR module is straight forward: Add the ZIP files as dependencies and use the dependency plugin to unzip it into the target/projectName folder:



That’s it! Now your HTML5 front-end team can work completely independently from your Java back-end team. And both teams will use the existing Maven repository.