2012
DOI: 10.1007/978-3-642-33427-6_1
|View full text |Cite
|
Sign up to set email alerts
|

Automatic Code Generation for the Orchestration of Web Services with Reo

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
31
0
1

Year Published

2012
2012
2019
2019

Publication Types

Select...
5
1

Relationship

4
2

Authors

Journals

citations
Cited by 26 publications
(32 citation statements)
references
References 9 publications
0
31
0
1
Order By: Relevance
“…Moreover, Reo has a formal foundation, which enables formal analysis of connectors (e.g., model checking [41]). This makes statically verifying that a given protocol does not dead- Reo has been successfully used as a language for expressing orchestration protocols for composition of Web services [37,38]. The previous software engineering advantages of Reo aside, one of the main differences between Reo and Bpel [53], generally considered the most important orchestration language in industry [8,55], is that Reo is declarative [38]: in Reo, one specifies what-instead of howinteraction among services takes place.…”
Section: Contextmentioning
confidence: 99%
“…Moreover, Reo has a formal foundation, which enables formal analysis of connectors (e.g., model checking [41]). This makes statically verifying that a given protocol does not dead- Reo has been successfully used as a language for expressing orchestration protocols for composition of Web services [37,38]. The previous software engineering advantages of Reo aside, one of the main differences between Reo and Bpel [53], generally considered the most important orchestration language in industry [8,55], is that Reo is declarative [38]: in Reo, one specifies what-instead of howinteraction among services takes place.…”
Section: Contextmentioning
confidence: 99%
“…We also use the formal notation of constraint automaton [18] for specification of the external behavior of a service. In this formalism, a web service is represented as a sequence of operations in which there are some constraints defined on operations' invocation order [19]. …”
Section: Meta Datamentioning
confidence: 99%
“…There is therefore, a constraint automaton generated for each service which should be captured within the behavior registry. The data structure of this registry is formed of state tables which store current state, next state, ports (operation names) and data constraints of constraint automaton [19]. Behavior registry of services is needed to generate final executable code for integrated services, as described in the next subsections.…”
Section: Registering Of Servicesmentioning
confidence: 99%
See 2 more Smart Citations