Studio SSK Custom Bean Fails to Initialize After Import
The error application=PINTXXXX_WSS_To_ProcessUnity_Outbound - Custom step id=InitializeCoreSSK, ref=SSK109InitializeCore - Error while invoking bean, reason: Unresolved compilation problem
What it means
When a Studio integration imports a Custom SSK (Studio Starter Kit) bean like InitializeCoreSSK, Eclipse can compile cleanly in the IDE but Workday's deployed runtime still fails to initialize the bean because it can't resolve classes the bean depends on.
Troubleshooting
- Confirm the compile-time fix already applied: Project Explorer > right-click project > Properties > Java Build Path > Libraries > Add External JARs, and add every JAR the custom bean's source imports.
- Rebuild and redeploy the .clar package after adding the JARs, don't just save in Eclipse.
- If the runtime error persists after a clean compile, check whether the JARs added to the build path were also bundled into the exported .clar (external JARs referenced only on the local build path aren't automatically packaged).
- Confirm the target JDK matches Workday's supported version (JDK 8) under Window > Preferences > Java > Installed JREs, a mismatched compiler can produce class files the runtime can't load even though Eclipse shows no errors.
⚡ Quick fix
Re-export the .clar with the required JARs explicitly bundled (not just referenced on the local build path), then redeploy.
✓ Permanent fix
Standardize the Studio project's build path and bundled-library list before customizing any Starter Kit bean, and pin the project's JDK compliance level to Workday's supported version so future SSK imports don't silently compile against the wrong runtime target.
Was this helpful?