Bridge that plugs
to obtain enhanced version of
Please see the
to read about many interesting use-cases.
To access GraalVM languages
To create new instance script engine manager ready for the NetBeans
execution environment use
class offers static
createManager() method that
should be used whenever one needs an instance of
inside of NetBeans based application.
Many client oriented use-cases are covered in the
Re-export of GraalVM languages
This module re-exports all found GraalVM languages under
GraalVM:lang name and makes them accessible via
Use Graal SDK directly
This module re-exports
Use them to obtain access to the GraalVM directly, if you only
want to work with them and generic
wrapper isn't enough.
This table lists all of the module exported APIs
defined stability classifications. It is generated
based on answers to questions about the architecture
of the module. Read them all
Group of java interfaces
Group of property interfaces
|Interface Name||In/Out||Stability||Specified in What Document?
When this module is used (on GraalVM or
it automatically exports all available languages (obtained via
instances. These dynamically created engines use
GraalVM:python) in their
By default all the GraalVM engines
run in a very restricted, secure sandbox. See
for details. That means the languages cannot
access local files, ports, etc. Some languages (like
implementation of the R language) need such access. In such
case one has to allow such access. This can be done by
var eng = Scripting.createManager().getEngineByMimeType("application/x-r");
eng.getContext().setAttribute("allowAllAccess", true, ScriptContext.GLOBAL_SCOPE)
Where are the sources for the module?
The sources for the module are in the
NetBeans Mercurial repositories.
What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?
XXX no answer for deploy-dependencies
Read more about the implementation in the answers to