Clone this repo:


  1. a7233c7 Updating badges for org-apache-sling-scripting-esx by Radu Cotescu · 9 months ago master
  2. f092ad7 SLING-7245 - Validate pull requests using Jenkins by Robert Munteanu · 9 months ago
  3. 61ebe42 trivial: added license header to *.md files by Radu Cotescu · 1 year, 1 month ago
  4. faceeea SLING-7215 - [nice-to-have] Add a CONTRIBUTING file to every module by Radu Cotescu · 1 year, 1 month ago
  5. 8dd58f9 SLING-7216 - [nice-to-have] Add a CODE_OF_CONDUCT file to every module by Radu Cotescu · 1 year, 1 month ago

Build Status License scripting

Apache Sling Scripting ESX

This module is part of the Apache Sling project.

A Node JS (like) module loader for Apache Sling.

This module is considered experimental for now.


This module implements a Nashorn Apache Sling Script Engine for the “esx” extension.

It requires a function named render in the esx script that processes the request.


The bundle must be installed before this bundle, to export the jdk.nashorn.api.scripting package.

Currently this implementation requires java version “1.8.0_92” or higher


Once this bundle is active you can try the engine with this minimal (and not very interesting) example:

First create a node with some content:

curl -u admin:admin \
  -F"sling:resourceType=foo" \
  -Ftitle="Hello ESX" \
  -Ftext="Here's some example text" \

Then create an ESX script to render it:

$ cat << EOF > /tmp/foo.esx
var foo = {
  render: function () {
    var output  = \`<h1>\${}</h1>\`;
    output +=;
    return output;     
module.exports = foo;

$ curl -u admin:admin -T /tmp/foo.esx http://localhost:8080/apps/foo/foo.esx

$ curl http://localhost:8080/apps/foo.html
<h1>Hello ESX</h1>Here's some example text

An ESX file is a regular java script file.

The NodeJS module resolution ( is implemented to give access to the rich collection of Node modules.

There's currently no priority handling of global modules.

The engine searches for scripts in the following order, if the regular module resolution does not find a module: - /apps/esx/node_modules - /apps/esx/esx_modules - /libs/esx/node_modules - /libs/esx/esx_modules

Additionally, ESX will try to resolve the folder esx_modules prior to node_modules.

Special Loaders

Require Extensions are deprecated (see, therefore we have not implemented/used the extension loaders api and .bin extension cannot be used.

We have borrowed the requirejs loader plugin syntax instead (see Additionally to the standard JS loader following two loaders are existing:

  • text (e.g. require("text!./templates/header.html")))

    • will return a javascript native string containing the content of the file
  • resource (e.g. require("resource!./content/blogposts)) following will be exposed:

    • properties (resource valuemap)
    • path (jcr path)
    • simpleResource (has getChildren method with resolved simpleresoruce in an array)
    • array with list of children (simpleResource)
  • json loader (e.g. require("./dict/en.json)

    • the json as a whole will be exported as a javascript Object

Demo Application

Currently the demo application is bundles with the engine bundle.

open http://localhost:8080/libs/esx/demo/content/demo.html

Writing a module

You can actually follow the NODE JS description on for more detailed explanation.

A module has access to following variables:

  • __filename
  • __dirname
  • console (console.log is a log4j logger registered to the resolved module path and is not a 1:1 console.log implementation for now)
  • properties (valuemap)
  • simpleResource
  • currentNode
  • currentNode.path
  • currentNode.resource
  • sling (SlingScriptHelper)


Caluclator Module

Path: /apps/demo/components/test/helper/calculator/index.js

function calculate(a, b) {
  return a + b;
exports.math = calculate;

Test components

Path: /apps/demo/components/test/test.esx

var calculator = require("./helper/calculator");

exports.render = function () {
  return calculator.math(2,2);