Js Rust Reference Documentation
Js
Current Version: 11.6.1
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
// Cargo.toml:
// [dependencies]
// chilkat = "11.6"
use chilkat::Js;
// Once per process, before any other Chilkat call:
chilkat::unlock_bundle("Anything for 30-day trial")?; // shorthand for Global::new().unlock_bundle(..)
let js = Js::new();
// ... the native object is freed when `js` goes out of scope.Creates the underlying native Chilkat object (Js also implements Default). Every method takes &self, so the object never needs to be declared mut. A Js is Send but not Sync: it may be moved to another thread, but a reference to it cannot be shared between threads at the same time.
The native object is freed when the Js is dropped — when it goes out of scope, or explicitly with drop(js). There is no Dispose method to call.
Errors
Methods that can fail return chilkat::Result<T>, which is Result<T, chilkat::Error>: a method whose only outcome is success or failure returns Result<()>, a method producing a string or an object returns Result<String> or Result<Js>. The error carries the object's LastErrorText at the time of the failure (Error::last_error_text), the class and method names, and implements std::error::Error, so ? works in any function returning chilkat::Result or a Box<dyn Error>. Properties never fail, and methods that answer a question (has_..., is_..., ...) return a plain bool.
match js.some_method(...) {
Ok(value) => println!("{value:?}"),
Err(e) => eprintln!("{}", e.last_error_text()),
}Properties
DebugLogFilePath
pub fn debug_log_file_path(&self) -> String
pub fn set_debug_log_file_path(&self, value: &str)
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
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
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
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
pub fn last_method_success(&self) -> bool
pub fn set_last_method_success(&self, value: bool)
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
pub fn timeout_seconds(&self) -> i32
pub fn set_timeout_seconds(&self, value: i32)
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
pub fn verbose_logging(&self) -> bool
pub fn set_verbose_logging(&self, value: bool)
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
Methods
CallFunction
Calls a JavaScript function. The function name and arguments are passed in func_json. The result is returned in result_json.
Returns Ok(()) for success, Err(chilkat::Error) for failure.
ConsoleOutputSb
Eval
Run jscript as a script. Return output and errors in result_json.
Returns Ok(()) for success, Err(chilkat::Error) for failure.
SetCkPermission
Sets sandbox related permissions for Chilkat objects. The chilkat_class_name is the name of the Chilkat class (case-insensitive), such as Http, Rest, "MailMan", "Ftp2", "Ssh", etc. The chilkat_class_name 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 .
Returns Ok(()) for success, Err(chilkat::Error) for failure.