Drools allows remote clients to use exactly the same API by using a
command approach. We have a client-side implementation of the drools
session api that simply creates command objects that can be serialized
and then transported from client to server using most communication
channels. At server side, commands can be restored and executed on the
session. I assume other solutions are possible as well, but this
approach should allow you to get started easily.
Kris
Quoting magicalpig <kingfelix(a)monarchy.com>:
I'm considering Drools Flow for a project that requires a workflow
enactment
engine. One concern I have is how much effort it might take to make
remote
calls to the engine. I plan on running the engine in its own JVM. I
would
then like for servlets to talk to the engine, for instance to tell it
that
Work Item XYZ has been completed successfully. It doesn't seem as
though any
API is exposed for remote clients though. Would I have to write my
own
interface which listens for the RMI calls from the servlets and then
maps
them to calls to the native API of the Drools Flow engine?
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-Remote-AP...
Sent from the Drools - User mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm