New Workflow API_148406415
Created by Tony Lam, last modified on Apr 28, 2010
This page describes the design of the next generation of Workflow API
The RMI solution can be done simply with Spring: http://static.springsource.org/spring/docs/2.5.6/reference/remoting.html. However, when passing a domain object to the remote service, it throws UnmarshalException. It is a problem in OSGi, and their suggestion is to use the OSGi remote service.
See: http://forum.springsource.org/showthread.php?t=56325 https://mail.osgi.org/pipermail/osgi-dev/2008-December/001558.html http://www.techinfopad.com/spring/101600181-spring-dm-and-rmiproxyfactorybean.html Model:
Image:attachments/148406415/148635649.png Distributed Workflow:
Image:attachments/148406415/148635650.png
- A workflow is a linear series of tasks
- The workflow object can be executed on the GumTree server (headless node)
- Workflow should be serialisable over RMI, etc
- Workflow can be constructed by Spring XMl configuration
- Import and export of workflow is done by XML, using XStream
- Workflow can be executed differently by using different executing strategy
- Workflow can be executed directly, or in a managed mode by the workflow execution manager
The RMI solution can be done simply with Spring: http://static.springsource.org/spring/docs/2.5.6/reference/remoting.html. However, when passing a domain object to the remote service, it throws UnmarshalException. It is a problem in OSGi, and their suggestion is to use the OSGi remote service.
See: http://forum.springsource.org/showthread.php?t=56325 https://mail.osgi.org/pipermail/osgi-dev/2008-December/001558.html http://www.techinfopad.com/spring/101600181-spring-dm-and-rmiproxyfactorybean.html Model:
Image:attachments/148406415/148635649.png Distributed Workflow:
Image:attachments/148406415/148635650.png
(image/png)
(image/png)
Document generated by Confluence on Apr 01, 2015 00:11