First I had to find the coresponding class of the jjs tool. I’m not sure I found the right one, but I did find a Shell class within the nashorn.jar file. Starting that class within intelliJ provided me a shell which was called jjs (so it cannot be that wrong). Sadly, not all the command line parameters that jjs has, worked on this class. Especially the “-e” was missing. That parameter is used to evaluate whatever inline script given through this parameter. Instead I had to fallback to files, to provide the launcher code for my actual application. This is what the launch configuration in intelliJ looks like.
Including this script, the launch configuration had to be adjusted with the correct script filename.
So now I could start my application through the launch configuration and in effect have a shell to interact with my code base at run-time.
- invoking java gc through bash
- Java SPI - a simple hello world service
- FormDataHandler implements com.sun.net.httpserver.HttpHandler
- ant task to show content of a jar file
- add jar to the classpath at runtime in jjs (the hacky way)
- doing objects in jjs
- read the content of a file in one line in jjs
- print something to the console in jjs
- using jjs under osx
- improve TIBCO Designer tester performance under linux