Author: vanto
Date: Mon Dec 31 15:38:58 2012
New Revision: 1427154
URL: http://svn.apache.org/viewvc?rev=1427154&view=rev
Log:
formatting tweaks.
Modified:
ode/site/trunk/content/instance-replayer.mdtext
Modified: ode/site/trunk/content/instance-replayer.mdtext
URL:
http://svn.apache.org/viewvc/ode/site/trunk/content/instance-replayer.mdtext?rev=1427154&r1=1427153&r2=1427154&view=diff
==============================================================================
--- ode/site/trunk/content/instance-replayer.mdtext (original)
+++ ode/site/trunk/content/instance-replayer.mdtext Mon Dec 31 15:38:58 2012
@@ -113,9 +113,9 @@ You can migrate a few instances at once
* It implements ReplayerScheduler, which executes actions from past in time
sorted order (exchanges given to replayer have createTime field, which is used
for sorting)
* jobs from past are processed in ReplayerScheduler and jobs in future are
registered in engine's scheduler
* In order to make integrity constraints, replaying returns error if:
- * a first incoming request is routed to an existing instance instead of
creating a new one
- * next incoming request is routed to other instance or creates a new instance
- * there is some unprocessed communication while finishing replaying (for
example if there is some outgoing exchange for service, which did not have
INVOKE from replayed instance)
+ - a first incoming request is routed to an existing instance instead of
creating a new one
+ - next incoming request is routed to other instance or creates a new instance
+ - there is some unprocessed communication while finishing replaying (for
example if there is some outgoing exchange for service, which did not have
INVOKE from replayed instance)
* It extends bpel-compiler and xpath evaluation by $ode:currentEventDateTime
variable
* It adds currentEventDateTime property to BpelRuntimeContext
* It adds replayer package to bpel engine in bpel-runtime module
