Java Libraries and Objects
Use the Code group to load approved Java libraries and exchange data with their classes and methods. These activities are intended for integrations that require a Java SDK or domain object that is not available through a standard connector.
Available activities
| Activity | Purpose |
|---|---|
| Java Library | Defines checksum-pinned Maven coordinates and the classloader used by Java object activities |
| Init Bean | Creates a Java object and returns a handle to it |
| Invoke Method | Invokes an instance or static Java method through the selected library classloader |
| JSON To Bean | Binds structured workflow data to a Java type |
| Bean To JSON | Serializes a Java object back to workflow data |
Typical flow
- Add a Java Library resource and specify approved, version-pinned dependencies.
- Use JSON To Bean or Init Bean to create the required object.
- Use Invoke Method to call the SDK or library operation.
- Use Bean To JSON to convert returned objects into mappable workflow data.
- Release or stop using object handles as soon as the workflow no longer needs them.
Governance and compatibility
- Pin dependency versions and checksums; do not load mutable or unreviewed artifacts.
- Confirm that classes and methods are compatible with the platform Java runtime.
- Avoid libraries that start unmanaged threads, modify global state, or terminate the process.
- Treat reflection-based method access as privileged functionality and expose only required classes.
- Keep large binary objects outside workflow state when a stream or managed file reference is available.
- Regression-test serialization whenever a library version changes.