Running Camel Routes as JavaScript Application with Nashorn and Nasven

November 9, 2015

Tags: #nashorn #javascript #nasven #camel #integration

I’ve already been thinking about this for a couple of months:

Running Apache Camel routes from/with Nashorn&JavaScript

Whyever, I didn’t find the time and/or impulse to start doing this yet.

During last week, I stumbled upon an article of camel.js, a re-implementation of Camel for Node.js. While this is a nice approach, and I really appreciate this, it’s not Camel itself and all the components and options of Camel are not there and has to be implemented again. But in Camel there’s also so much intelligence and work incorporated - why doing this again!?

Additionally, there’s Nasven - a tool to get Maven artifacts in scope for Nashorn script execution. It’s created by Bruno Borges, a Product Manager and Developer working for Oracle.

So, with that, I thought, it should be easy to do. And indeed, it is! I’ve created a Camel example for Nasven, using the Camel core library executing a simple route moving a file from a to b. Nothing special, but shows how easy it is to use Camel from JavaScript. Just create your routes and run the application. No compile time any more, no expensive and long deployment cycles - just edit your route if necessary and restart the application and - pow! - you are done!

Just create a package.json file with the dependency to the camel-core lib:

  "dependencies": {
    "maven": [

The actual application takes place in the index.js file:

var Main =;
var RouteBuilder =;
var myRouteBuilder = Java.extend(RouteBuilder);
var route = new myRouteBuilder() {
  configure: function() {
    var sup = Java.super(route);
var mainCamel = new Main();

As you can see, no rocket-science, no magic, just JavaScript code!

To run/execute the application, you have to have Nasven installed on your machine. Then, just type at the command line from within the appropriate folder:

$ nasven package.json

With this, you can e.g. automate as much tasks as you like to get things done in your environment, just from the command line! :-)

« JavaOne - it's all about Community! First Conference Talks 2016 announced »