Recent changes to Syntax

WikiPage Syntax modified by Bruce Kissinger

Bruce Kissinger — Thu, 28 Jun 2012 17:52:44 -0000

--- v2
+++ v3
@@ -22,135 +22,3 @@
 This defines a context variable named persons which is assigned an initial value of 0.
 Next, the controlflow includes a step that manipulates the context variable and sets the value of persons to 2.
 
-***
-
-Loop Example
----
-
-In this example, a variable named counter is defined and assigned the initial value of 1. An endpoint is also defined that displays the current date/time.  The control flow consists of three activities.
-
-
-An activity statement calls an endpoint that displays the current time.
-A cycle statement defines the begining of a loop which will execute while the counter value is less than 10000.
-An activity statement increments the value of the counter variable
-When the cycle completes, the timer endpoint is called again
-
-
-    %
-    % Test performance of large loops
-    %
-    endpoint :simpletimer => erl://simpletimer:display
-    context :counter => 1
-
-    controlflow do
-    
-    	% call the timer endpoint to display the current time
-    	activity :starttime, :call, simpletimer
-    	end
-    
-    	% main loop
-    	cycle (@counter < 10000) do
-    		activity :increment, :manipulate do
-    			@counter += 1
-    		end
-    	end
-    
-    	% call the timer endpoint to display the current time
-    	activity :endtime, :call, simpletimer
-    	end
-    end
-
-
-***
-
-Parallel Activities
----
-In this example, three HTTP endpoints are defined. A parallel activity is specified and the ":wait" clause tells the engine to wait until all parallel branches have completed.
-
-
-    endpoint :endpoint1 => http://localhost/endpoint1
-    endpoint :endpoint2 => http://localhost/endpoint2
-    endpoint :endpoint3 => http://localhost/endpoint3
-    
-    controlflow do
-    	
-    	parallel :wait do
-    	
-    		% operates in a seperate thread -- this should complete first
-    		parallel branch do
-    			activity :branch1a1, :call, endpoint1
-    			end
-    			
-    			activity :branch1a2, :call, endpoint2
-    			end
-    		end
-    		
-    		% operates in a seperate thread - this should complete last because 
-    		% endpoint3 takes a long time to execute
-    		parallel branch do
-    			activity :branch2a1, :call, endpoint3
-    			end
-    		end
-    
-    	end
-    	
-    	% this should not be run until both parallel branches have completed
-    	activity :trace, :manipulate do
-    		show runtime_context
-    	end
-    
-    end
-
-Note that the statement show runtime_context causes the values of any context variables to be displayed.
-
-***
-
-Web Service Example
----
-
-In this example, a Google currency conversion service is called. The control flow consists of three activities.
-
-
-First, the query for the URL is constructed by several manipulate activities.
-Next, the web service is invoked and the query is passed as parameter. The query results are copied to a variable named "returnValue".
-Finally, some processing of the returned values would be performed.
-
-
-    % 
-    % Demonstrate currency conversion using a Google service
-    %
-
-    endpoint :currencyConversion => http://www.google.com/ig/calculator
-    
-    context :amount => '100'
-    context :fromCurrencyCode => 'USD'
-    context :toCurrencyCode => 'INR'
-    context :urlQuery => nil
-    context :returnValue => nil
-    
-    controlflow do
-    	%
-    	% build the URL query string which should look like
-    	%   hl=en&q=100USD=?INR
-    	%
-    	activity :build1, :manipulate do
-    		@urlQuery = 'hl_en&q=' + @amount
-    	end
-    	activity :build2, :manipulate do
-    		@urlQuery = @urlQuery + @fromCurrencyCode
-    	end
-    	activity :build3, :manipulate do
-    		@urlQuery = @urlQuery + '=?'
-    	end
-    	activity :build3, :manipulate do
-    		@urlQuery = @urlQuery + @toCurrencyCode
-    	end
-    	
-    	% call the currency conversion service
-    	activity :getConversion, :call, currencyConversion, @urlQuery do |results| 
-    		@returnValue = results
-    	end
-    	
-    	% do something with the currency return results
-    end
-

WikiPage Syntax modified by Bruce Kissinger

Bruce Kissinger — Tue, 19 Jun 2012 15:36:40 -0000

--- v1
+++ v2
@@ -102,3 +102,55 @@
     end
 
 Note that the statement show runtime_context causes the values of any context variables to be displayed.
+
+***
+
+Web Service Example
+---
+
+In this example, a Google currency conversion service is called. The control flow consists of three activities.
+
+
+First, the query for the URL is constructed by several manipulate activities.
+Next, the web service is invoked and the query is passed as parameter. The query results are copied to a variable named "returnValue".
+Finally, some processing of the returned values would be performed.
+
+
+    % 
+    % Demonstrate currency conversion using a Google service
+    %
+
+    endpoint :currencyConversion => http://www.google.com/ig/calculator
+    
+    context :amount => '100'
+    context :fromCurrencyCode => 'USD'
+    context :toCurrencyCode => 'INR'
+    context :urlQuery => nil
+    context :returnValue => nil
+    
+    controlflow do
+    	%
+    	% build the URL query string which should look like
+    	%   hl=en&q=100USD=?INR
+    	%
+    	activity :build1, :manipulate do
+    		@urlQuery = 'hl_en&q=' + @amount
+    	end
+    	activity :build2, :manipulate do
+    		@urlQuery = @urlQuery + @fromCurrencyCode
+    	end
+    	activity :build3, :manipulate do
+    		@urlQuery = @urlQuery + '=?'
+    	end
+    	activity :build3, :manipulate do
+    		@urlQuery = @urlQuery + @toCurrencyCode
+    	end
+    	
+    	% call the currency conversion service
+    	activity :getConversion, :call, currencyConversion, @urlQuery do |results| 
+    		@returnValue = results
+    	end
+    	
+    	% do something with the currency return results
+    end
+

WikiPage Syntax modified by Bruce Kissinger

Bruce Kissinger — Tue, 19 Jun 2012 15:33:25 -0000

General --- Workflow steps are contained within a single text file. Each text file consists of one or more lines that define:

handlers (optional)
endpoints (optional)
context variables (optional)
control flow statements (required)

For example, a simple workflow might look like this: context :persons => 0 controlflow do activity :step1, :manipulate do @persons = 2 end end This defines a context variable named persons which is assigned an initial value of 0. Next, the controlflow includes a step that manipulates the context variable and sets the value of persons to 2. *** Loop Example --- In this example, a variable named counter is defined and assigned the initial value of 1. An endpoint is also defined that displays the current date/time. The control flow consists of three activities.

An activity statement calls an endpoint that displays the current time.
A cycle statement defines the begining of a loop which will execute while the counter value is less than 10000.
An activity statement increments the value of the counter variable
When the cycle completes, the timer endpoint is called again

% % Test performance of large loops % endpoint :simpletimer => erl://simpletimer:display context :counter => 1 controlflow do % call the timer endpoint to display the current time activity :starttime, :call, simpletimer end % main loop cycle (@counter < 10000) do activity :increment, :manipulate do @counter += 1 end end % call the timer endpoint to display the current time activity :endtime, :call, simpletimer end end *** Parallel Activities --- In this example, three HTTP endpoints are defined. A parallel activity is specified and the ":wait" clause tells the engine to wait until all parallel branches have completed. endpoint :endpoint1 => http://localhost/endpoint1 endpoint :endpoint2 => http://localhost/endpoint2 endpoint :endpoint3 => http://localhost/endpoint3 controlflow do parallel :wait do % operates in a seperate thread -- this should complete first parallel branch do activity :branch1a1, :call, endpoint1 end activity :branch1a2, :call, endpoint2 end end % operates in a seperate thread - this should complete last because % endpoint3 takes a long time to execute parallel branch do activity :branch2a1, :call, endpoint3 end end end % this should not be run until both parallel branches have completed activity :trace, :manipulate do show runtime_context end end Note that the statement show runtime_context causes the values of any context variables to be displayed.