Js Chilkat2 Java Reference Documentation
Js
Current Version: 11.7.0
Markdown version of this page for AI tools (v 11.7.0) · all AI docs
Chilkat.Js
Use
Run JavaScript code from inside the host application without launching an
external scripting process.
Start from a restricted execution environment and selectively expose only
the capabilities the script should use.
Allow scripts to use selected Chilkat classes when the host application
wants JavaScript to perform controlled Chilkat operations.
Optionally restrict filesystem access so scripts can read or write only
within approved locations.
Execute JavaScript, pass data through the host-controlled environment,
and retrieve results or diagnostics from the script run.
Use JavaScript as an embedded extension language for application-defined
workflows while keeping host resources protected.
For an extended overview, see
Js Class Overview.
Also see
About the Chilkat.Js JavaScript Engine.
Execute sandboxed JavaScript inside an application with controlled access to Chilkat features.
Chilkat.Js when an application needs to execute JavaScript
internally while retaining control over what the script is allowed to access.
By default, scripts run in a closed sandbox with the JavaScript language and
standard library available, but without filesystem, network, or Chilkat
class access unless the host application explicitly enables those
capabilities.
Embedded JavaScript engine
Sandboxed by default
Enable Chilkat classes
Filesystem restrictions
Script input and output
Controlled automation
Js object, load or provide the JavaScript code, enable
only the Chilkat classes and filesystem locations the script is permitted to
use, run the script, and inspect the result or diagnostic output. Use
Chilkat.Js when the application needs scriptability with a
security boundary controlled by the host.
Object Creation
import com.chilkatsoft.chilkat2.ChilkatException;
import com.chilkatsoft.chilkat2.Js;
try (Js js = new Js()) {
// ... use js ...
} catch (ChilkatException e) {
System.out.println(e.getMessage()); // "Js.someMethod failed: <reason>"
System.out.println(e.getLastErrorText()); // the full log of the failed call
}Creates the underlying native Chilkat object. The native library (chilkat2java) is loaded the first time any Chilkat2 object is created; see the README in the download for where it is looked for (-Dchilkat2.library.path, a classpath resource, or java.library.path).
Releases the native object (Js is AutoCloseable, so try-with-resources calls it). Calling it again does nothing; any other method or property accessor called afterwards throws IllegalStateException. An object that is never closed is freed by a background cleaner once it becomes unreachable, but the garbage collector does not see native memory, so closing is the normal path. Objects returned by methods are owned by the caller too.
Returns true once close() has been called.
Errors
A method that fails throws ChilkatException, an unchecked exception carrying getClassName(), getMethodName(), getReason() (one line, also in the message) and getLastErrorText() (the full log, captured at the moment of the failure). The object remains usable. Methods that look something up and find nothing return null instead of throwing (each such method says so), and methods that answer a question (hasMember, isUnlocked, ...) return a plain boolean. Property accessors do not throw for Chilkat reasons.
A null string or object argument throws NullPointerException naming the parameter (except where a method documents that null is accepted), and a string containing U+0000 throws IllegalArgumentException.
Use an object from one thread at a time; it may be handed from one thread to another. The one cross-thread operation is setting setAbortCurrent(true) on an object that is busy in another thread (on the classes that have AbortCurrent). Unlocking: call new Global().unlockBundle("...") once at startup.
Properties
DebugLogFilePath
String getDebugLogFilePath()
void setDebugLogFilePath(String value)
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
LastErrorHtml
String getLastErrorHtml()
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
String getLastErrorText()
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
String getLastErrorXml()
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
boolean getLastMethodSuccess()
void setLastMethodSuccess(boolean value)
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.
TimeoutSeconds
int getTimeoutSeconds()
void setTimeoutSeconds(int value)
Specify a timeout in seconds to prevent JavaScript from running indefinitely, such as in an infinite loop. By default, the value is 0, meaning no timeout is set and infinite loops will continue forever.
VerboseLogging
boolean getVerboseLogging()
void setVerboseLogging(boolean value)
If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
String getVersion()
Methods
CallFunction
Calls a JavaScript function. The function name and arguments are passed in funcJson. The result is returned in resultJson.
Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.
ConsoleOutputSb
Eval
Run jscript as a script. Return output and errors in resultJson.
Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.
SetCkPermission
Sets sandbox related permissions for Chilkat objects. The chilkatClassName is the name of the Chilkat class (case-insensitive), such as Http, Rest, "MailMan", "Ftp2", "Ssh", etc. The chilkatClassName can also be set to "all" to apply the permission to all Chilkat classes.
Possible values for permission are:
disable- Your JavaScript code is not allowed to create an instance of the Chilkat class. A JavaScript exception is thrown when trying to create a Chilkat object of a class that is disabled.sandbox- Objects for the Chilkat class can be instantiated in JavaScript, but they have no read or write access to the local filesystem.readOnly- Objects for the Chilkat class can be instantiated in JavaScript and have read-only access to the local filesystem.writeOnly- Objects for the Chilkat class can be instantiated in JavaScript and have write-only access to the local filesystem.readWrite- Objects for the Chilkat class can be instantiated in JavaScript and have read/write access to the local filesystem.
By default, all Chilkat classes are disabled. Your application must enable "all" or specific Chilkat classes before calling Eval or CallFunction .
Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.