Using a directive for HawtIO

As I have written in an earlier post my recent project work allowed me to spend some time contributing to hawtio. Out of personal interest I have migrated some older code I had to analyze OSGI dependencies to a hawtio plugin. It took me a bit to figure out how to do that living up to the Angular idea of MVC separation. As it turned the contribution ended up in two plugins:

  • One tapping into the backend data collecting the OSGi metadata and preparing the graph data
  • One plugin providing an Angular directive to render the graph data using a D3 force graph layout.

This article will look at some details of the rendering directive as that might provide some help for others trying to write a directive. This article is not intended as a Angular or Typescript tutorial, please refer to the Angular directive documentation or the Typescript documentation for that.

The complete code and users guide for the directive is located within the hawtio project on github. You may want to read that bit first before you read on…

Using the directive

Angular directives are used to take an arbitrary data structure from the model (in Angular that is the $scope). In our case we want to be able to stick a data structure that representing a graph with nodes and edges into the directive and expect the directive to take care of all the required rendering magic, in that particular case operating the D3 API.

Assuming that our scope has a member called graph, we want to use the following HTML code to display it:

<div hawtio-force-graph
  style="min-height: 800px" />

hawtio-force-graph is the name of the directive to render the graph. The example above uses the graph data within the current controller’s scope and passes that into the graph attribute of the directive. You see that the directive has other attributes that will be available within the directive code to drive the rendering.

Registering the Directive

Each directive must be registered with the Angular framework, so that it can be found whenever HTML code like the above is encountered. Registering a directive is as simple as instantiating a class and stick it into the Angular framework:

module ForceGraph {
var pluginName = 'forceGraph';

  angular.module(pluginName, ['bootstrap', 'ngResource', 'hawtioCore']).

  directive('hawtioForceGraph', function () {
    return new ForceGraph.ForceGraphDirective();


It is best practice that the code for one plugin is organized within a corresponding module, in this case the modules name is ForceGraph. The actual code simply uses the module function of angular to create the module and the directive within. The name of the directive, in our case hawtioForceGraph is what defines the name of the attribute within the div element. The is specified in camel case within the code, but normally is used with dashes within the HTML code. For the name a function is registered that returns an instance of the class implementing the directive.

At last the module must be registered with the hawtio plugin loader.

A look at the directive class

The class is defined in it’s own file. The file contains a lot of D3 specific code to render the graph data structure accordingly. Relevant for the directive plumbing are just a couple of attributes within the directive class. These attributes correspond to the attributes within a directive definition object as specified in the Angular documentation.

module ForceGraph {

  export class ForceGraphDirective {

    public restrict = 'A';
    public replace = true;
    public transclude = false;

    public scope = {
      graph : '=graph',
      nodesize : '@',
      linkDistance : '@',
      charge : '@'

    public link = ($scope, $element, $attrs) => {

      $scope.trans = [0,0];
      $scope.scale = 1;

      $scope.$watch('graph', (oldVal, newVal) => {

// ... Many lines ommitted


Let’s walk through these bits one by one:

  1. The restrict attribute defines the context in which the directive can be used. “A” in this case allows the usage as an attribute, which is also the default for directives.
  2. The setting replace = true specifies that the div element containing the directive is replaced with whatever the directive generates.
  3. transclude = false indicates that content within the div element will not be available within the directive. In our case that makes sense as the relevant graph data is passed as a scope attribute.
  4. The scope attribute defines an isolated scope. In other words, only stuff that we stick into the scope from within the directive or pass in as attributes will be available within the $scope object variable. Within the scope, graph: “=graph” denotes that the graph object of the outer scope is passed into the graph variable of the directive. All attributes simply referenced via an ‘@’ on the right hand side will be passed in as values from div element attributes with the same name.
  5. The link function actually performs the rendering. In our case we set up a watch on the graph variable of the directive, so that angular executes updateGraph() whenever that variable changes. As the variable is bound to the outer scope, the graph will be re-rendered whenever the underlying graph data changes.

The end

That concludes our quick walk through the force graph directive plugin. Next time I will walk though the data factory that provides the graph data and how that factory is used to create the graph data structure.