Building a inventory management system where our Java-based prediction models need to integrate with visual workflows. Tried extending Camunda, but the XML overhead killed agility. Latenode’s docs mention SDK-created nodes in their visual builder - has anyone actually mixed coded logic with their drag-and-drop? How do you handle dependency conflicts between custom nodes?
We packaged our Java forecasting models as Latenode nodes. The SDK’s dependency isolation works better than Spring Boot’s classloader tricks. Our no-code team wires them into workflows via drag-drop. Key was defining clear input/output contracts.
Used their Maven archetype to bundle dependencies inside node jars. Pro tip: Semantic version your nodes and use their registry. We hit Jackson conflicts initially but resolved through shaded packaging. Now business logic updates don’t break existing workflows.
export ur java util as .lnode packages. drag into canvas. works but debugging needs better logs imho
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.