Define a set of common runtime services for local/remote operations on Passerelle flows

[GoogleCodeExporter]

The RepositoryService and FlowManager APIs provide services to maintain 
versioned flows/models and to open them, execute them etc.

The FlowManager can also act as facade for a REST client, to 
browse/modify/execute models on a server-based runtime.
Other remoting protocols are used/needed in different contexts (JMX, SOAP, ...).
The RepositoryService currently has no remote implementation at all.

In other contexts (e.g. DAWN RCP, integration in SCADA control dashboards etc), 
some extensions and improvements on these APIs are needed.
At the same time, there has been some pollution during the years in the current 
service definitions.

So the goal of this task is to :
- define clean common service APIs for managing flows/models locally and 
remotely; i.e. interact with a repository for models and related assets.
- define clean common service APIs for running flows in different modes (e.g. 
stepping, breakpoints etc), incl support for stopping/pausing/resuming etc
- define extra runtime services for monitoring of and interacting with running 
flows
- implement all of the above for local operations and remote operations via 
JMX/REST/SOAP

Original issue reported on code.google.com by erwin...@gmail.com on 14 Apr 2013 at 2:25

[GoogleCodeExporter]

Original comment by erwin...@gmail.com on 14 Apr 2013 at 2:26

• Changed state: Started
• Added labels: Component-Logic, Maintainability, OpSys-All, Priority-High, Type-Enhancement
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Issue 53 has been merged into this issue.

Original comment by erwin...@gmail.com on 7 Aug 2013 at 9:28

[GoogleCodeExporter]

Original comment by erwin...@gmail.com on 18 Sep 2014 at 8:58

• Changed state: Done