I'm wondering where gwt-console and gwt-console-server sit in the scheme of things.
As far as I can see, gwt-console-server is a war packaged drools/jbpm server with a rest interface and gwt-console is a UI using that rest interface for the human interface interaction. Have I got this right?
I'm looking at how I need to integrate drools flow with our system and UI and believe I need my own human task queue implementation and interface. Are there parts of the human task stuff that I can re-use in my embedded application of jBPM?
Still trying to learn how it all fits together...
If you want to integrate the jBPM5 / Drools Flow Human Task functionality inside your apps I really recommend you to take a look at the Human Task APIs. They provide you all the things that you need in order to implement the same funtionality that you find inside the jBPM-Console, but technology agnostic (for front ends).
I hope it helps!
Yes, correct, the jbpm-console is a client that uses the gwt-console-server REST interface to interact with the engine. If you want to integrate your own application with the engine, you could:
- simply use the same REST interface to interact with the engine whenever appropriate
- directly access the underlying (and much more powerful) taskClient to interact with the human task service: