#Json query with scriptengine install#
#Json query with scriptengine driver#
#Json query with scriptengine code#

The compiled java classes must remain in this folder because when we start the JVM the C++ code looks into this folder for the Java classes. The source can be found unser src/mongo/java. The next step is to compile the Java code.

Modify these 4 lines to your environment:Д®nv.Append(CPPPATH = )Д®nv.Append(LIBPATH = )Д®nv.Append(LIBS = )ДЄfter these steps you can compile the code with scons. Currently it is configured for 64bit Windows. The configuration for the JVM begins at line 480 and ends at line 845. Important: you have to switch to the branch вЂњmongo_r255_jvmвЂќ.ДЄs the read me file describes you have to adopt the dir/SConstruct file so the c++ compiler can reference the JNI headers from your machine.

#Json query with scriptengine install#

The logic to access the database is in the MongoManager.java file and this class is available as the variable вЂmongo' from JS.ДЇirst you have to install the JDK 8 (or newer) and all the stuff which is required to build mongo (Scons/python etc. With Java8/Nashorn we can back up the JS objects by a Java class. (This is the first point which we should improve).

#Json query with scriptengine driver#

One problem was that we were not able to query the database from Java via JNI, so we decided to use a Java driver to mongo. Inside the JVM we start Nashorn which evaluates the JavaScript and pushes back the result to the C++ layer. Here we get the JavaScript code as a char* from Mongo, we do some stuff with it and then it is pushed to the JVM. The most important things happen in the invoke function of the FakeScope class. it should be something like JVMScriptEngine and JVMScope). The two classes which we completely modified are the V8Scope and the V8ScriptEingine and we replaced them with our FakeScope and FakeScriptEngine (which is pretty bad naming. This two classes are subclassed and the ScriptEngine is initialised with the actual Scope instance which is used by the JavaScript engine. The two classes which are responsible for the handling of all the JavaScript code are the ScriptEngine and the Scope classes.

The interesting part regarding the JavaScript evaluation can be found in the src/mongo/scripting/engine_v8.h (and in the engine_v8.cpp) files. The result of the examination of the source code: We checked out the tag 2.5.5 and we built all our modifications for this tag. We wanted to cut off V8 and start a JVM with the Nashorn JavaScript engine and every time when a stored procedure is used instead of a V8 call we wanted to push the JavaScript code to Nashorn evaluate it there and push the result back to Mongo. The original source code can be found here: (In MongoDB everything is stored as a JSON object and stored procedures are written in JavaScript) MongoDB is an open source C++ project hosted on GitHub and it currently uses GoogleвЂ™s V8 JavaScript engine to run the stored procedures. This post is a documentation/wrap up for that project. The goal was to see if the JavaScript engine of MongoDB could be replaced by a JVM based JavaScript engine and if so then building a prototype to show how this can be done. This semester I was a part of a small project with Oracle labs.