Sorry for the very late answer.
You can definitely use kie-services-remote in your application: however, figuring out all of the dependencies/artifacts/jars that it needs in order to work is a B$%#&.
kie-services-remotes relies on jbpm-kie-services for the most part -- in short, it's just a REST/JMS interface to the execution server.
You know, I came to exactly the same conclusion
I ended up re-implementing a subset of the basically the same commands, with some slightly customized calls. I could have gotten away with using the entire REST API from kie-services-remote - and I see lots of people on this forum trying to do the same thing. I think it would be handy to have a whole package I could add (maybe call it kie-services-remote-svc or something) that was set up to be pluggable into any web application already running KIE. This service would basically provide a callback or listener API that I could hook into to that would handle all the REST grok-age for me and I could concentrate on what I wanted to do.
That, and a beer, and I have all I need.
Thanks for replying.
I have no clue when we'll get the time to put this together -- although, it might not be that hard. That being said, could you add your opinion to the following:
If we put together a "kie-services-remote-svc" package (or whatever it ends up being called), is it correct to say that it would only supply the following:
1. REST services (obviously)
2. Underlying connection to the jBPM runtime/engine (basically, the jbpm-runtime-manager and jbpm-kie-services module), so that processes could be started, etc.
3. Deployment management, because 1 and 2 need that
This means, of course, no UI, no guvnor, no web-designer, etc.
Is that basically what you have in mind?
What you have described is effectively what I wrote . We use KIE Worbench straight out of the box to design processes, and then export them via GIT directly to our GUI-less stand alone execution engine. The engine is controlled with a REST API that we fiddle with via BASH scripts and our already-existing management GUI.
So yes, that is exactly what we have in mind.