This module provides a wrapper around JDK's
that is aware of NetBeans specific extensions. Please see the
to read about many interesting use-cases.
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
Dynamic registration of ScriptEngineFactory
and register it into global lookup via
to dynamically discover and offer new
to users of
Static registration of ScriptEngineFactory
To register additional scripting engine, just include its JAR file in
the application. Its factory registration in
will be found and used by
factory methods. Alternatively you can implement and register
as in the dynamic registration use-case.
In any case don't forget to advertise your engine to the
tag as specified by manifest registration
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?
If your module wants to use a script engine of given name,
then include a token dependency
in your manifest file (also accessible through project customizer GUI)
to indicate to the system that you need it.
- for example
Modules that provide implementations of enginesshould use
to advertise them. Only then
the runtime container
can make sure all requested providers
in the application are really enabled and the dependencies are
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