File: 1Mile.txt

package info (click to toggle)
virtuoso-opensource 6.1.6+dfsg2-4
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid, stretch
  • size: 260,992 kB
  • ctags: 125,220
  • sloc: ansic: 652,748; sql: 458,419; xml: 282,834; java: 61,031; sh: 40,031; cpp: 36,890; cs: 25,240; php: 12,692; yacc: 9,523; lex: 7,018; makefile: 6,157; jsp: 4,484; awk: 1,643; perl: 1,013; ruby: 1,003; python: 326
file content (62 lines) | stat: -rw-r--r-- 2,013 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62


BPEL implementation. draft. 1Mile


On the first stage we need to establish basic functionality of BPEL. This should include uploading BPEL projects, some simple but stateful model of BPEL processing. At least async "Hello World!" project must work. 


1. Generator

bif procedure for uploading BPEL process.

The Generator reads project .xml file (like in Collaxa) and finds .bpel and .wsdl files for BPEL process, generates all needed services and publishes them.

All BPEL driven services are stubs to one common processing service (Invoker) which handle the process state and continues freezed processes.

The process is represented by piece of persistent xml which will be used to make various actions.

The generator also checks .bpel .wsdl agains apropriate xml schema, performs several checks for logical consistency, fill tables with initial values. Puts the processor in the initial state.

2. Process Flow
Each process takes only one thread (or each user takes only one thread?).
At the special points (receive, invoke, link) flow creates wait object and tries to switch to concurrent operation. If there is no any concurrent operations the flow tries to find signaled waits, processes them, goes to freezed state.
Timeouts - put the wait into signaled state.

	2.1. Processing the signaled wait or the concurrent operation.
	Load the process flow xml. find the node. perform node's operations (assigment, invoke...).
	2.1.1 assigment. - obviously
	2.1.2 invoke. call remote service. wait for the result. if it is linked, put connected wait object into the signaled state.
	2.1.3 receive in code. create wait object.
	2.1.4 message has been received. search for the wait object. follows like 2.1.1

	2.2 <flow>
		
	2.3 <links>
	

3. scopes
scope represents the context of activity. Each variable, correlation resolved with scope prefix. Each scope has an reference to upper scope to establish nesting.

4. faultHandlers
will be in the 2Mile.

5. compensation
2Mile.