Transformation of an asynchronous transactional messaging language into a web services compatible language

• US 7,971,195 B2
• Filed: 02/02/2007
• Issued: 06/28/2011
• Est. Priority Date: 06/11/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: McCrady, Donald James, Ringseth, Paul F.
• Primary Examiner(s): Khatri; Anil
• Application Number:
  US11/670,440
• Publication Number:
  US 20070130571A1
• Time in Patent Office: 1,607 Days
• Field of Search: 717108-109, 717114-118, 717136-148
• US Class Current: 717/137
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Instructions in an asynchronous transactional messaging language are transformed into instructions that are compatible with the web services. In one embodiment, the asynchronous transactional messaging language is XLANG/s, and the web service languages are the web services description language (WSDL) and the simple object access protocol (SOAP). A programmer simply writes high level declarative statements that pertain to the specific type of business transaction. During compilation, selected instructions are transformed into instructions that are compatible with web services. This transformation is transparent to the designer of the business application. The asynchronous transactional messaging language source files are compiled in an iterative compilation process. During each pass of this compilation process, different variables are parsed. The parsed results are logically organized in a tree structure. The tree structure is traversed in depth first traversal order. During this traversal, instructions are transformed into instructions compatible with web services.

Claims

1. A computer-implemented method for transforming instructions in an asynchronous transactional messaging language to instructions compatible with web services, said method comprising:

iteratively translating, a predetermined number of times, via a processor, proxy class instructions of said asynchronous transactional messaging language into corresponding port type instructions compatible with said web services, wherein said predetermined number is determined in accordance with a level of dependency of variables within said asynchronous transactional messaging language;

transforming, via the processor, methods of said proxy class instructions into corresponding operations of said port types;

translating, via the processor, input parameters of said methods into corresponding request message types of said operations;

translating, via the processor, output parameters of said methods into corresponding response message types of said operations; and

storing the translated output parameters.

2. A method in accordance with claim 1, wherein said web services compatible instructions are compatible with a remote procedure call protocol.

3. A method in accordance with claim 2, wherein said remote procedure call protocol utilizes hypertext transport protocol (HTTP) as a transport and extensible markup language (XML) as a data format.

4. A method in accordance with claim 1, wherein said web services compatible instructions are compatible with a web services description language (WSDL)-like language.

5. A method in accordance with claim 1, wherein said web services compatible instructions are compatible with a simple object oriented protocol (SOAP)-like language.

6. A method in accordance with claim 1, wherein said asynchronous transactional messaging language is an XLANG/s-like language.

7. A method in accordance with claim 1, further comprising:

extracting a fully qualified method-type name from a name space of said method-type;

appending a prefix to said fully qualified method-type name, said prefix comprising double underscores followed by a term “

messagetype”

followed by a single underscore;

appending a suffix to said fully qualified method-type name, wherein;

if said method-type comprises an input parameter, said suffix comprises a single underscore followed by a term “

request”

; and

if said method-type comprises an output parameter, said suffix comprises a single underscore followed by a term “

response”

; and

replacing all periods in said fully qualified method-type name with a single underscore.

8. A computer-implemented method for compiling instructions in an asynchronous transactional messaging language, said method comprising:

iteratively compiling a predetermined number of times said instructions in said asynchronous transactional messaging language for providing compilation units, wherein said predetermined number is determined in accordance with a level of dependency of variables within said asynchronous transactional messaging language;

organizing said compilation units into a tree;

traversing said tree in depth first traversal order; and

translating selected encountered compilation units into corresponding second instructions compatible with web services.

9. A method in accordance with claim 8, said act of iteratively compiling comprises:

parsing using declarations, message types, correlationtypes and service names during a first pass;

parsing port types during a second pass;

parsing service link types during a third pass; and

parsing residual types and variables during a fourth pass.

10. A method in accordance with claim 8, wherein said act of translating comprises translating types, ports and messages in said asynchronous transactional messaging language into type instructions compatible with said web services.

11. A method in accordance with claim 8, wherein said act of translating comprises:

upon encountering all types associated with a service, translating method message types and class based port types appearing in service link types in said asynchronous transactional messaging language into corresponding types compatible with said web services; and

upon encountering subsequent services, translating method based messages and class based ports in said asynchronous transactional messaging language with types compatible with said web services.

12. A method in accordance with claim 8, wherein said second instructions are compatible with a remote procedure call protocol.

13. A method in accordance with claim 12, wherein said remote procedure call protocol utilizes hypertext transport protocol (HTTP) as a transport and extensible markup language (XML) as a data format.

14. A method in accordance with claim 8, wherein said second instructions are compatible with a web services description language (WSDL)-like language.

15. A method in accordance with claim 8, wherein said second instructions are compatible with a simple object oriented protocol (SOAP)-like language.

16. A method in accordance with claim 8, wherein said asynchronous transactional messaging language is an XLANG/s-like language.

17. A compiler for compiling instructions in an asynchronous transactional messaging language, said compiler comprising:

a code generator for;

iteratively compiling a predetermined number of times said instructions in said asynchronous transactional messaging language for providing compilation units, wherein said predetermined number is determined in accordance with a level of dependency of variables within said asynchronous transactional messaging language;

organizing said compilation units into a tree; and

traversing said tree in depth first traversal order; and

a transformer for translating selected encountered compilation units into corresponding second instructions compatible with web services.

18. A compiler in accordance with claim 17, said instructions being iteratively compiled, said compiler further comprising:

a parser for;

parsing using-declarations, message types, correlationtypes and service names during a first pass;

parsing port types during a second pass;

parsing service link types during a third pass; and

parsing residual types and variables during a fourth pass.

19. A compiler in accordance with claim 17, wherein said transformer transforms types, ports and messages in said asynchronous transactional messaging language into type instructions compatible with said web services.

20. A compiler in accordance with claim 17, wherein:

upon encountering all types associated with a service, said transformer transforms method message types and class based port types appearing in service link types in said asynchronous transactional messaging language into corresponding types compatible with said web services; and

upon encountering subsequent services, said transformer transforms method based messages and class based ports in said asynchronous transactional messaging language into types compatible with said web services.

21. A compiler in accordance with claim 17, wherein said web services compatible instructions are compatible with a remote procedure call protocol.

22. A compiler in accordance with claim 21, wherein said remote procedure call protocol utilizes hypertext transport protocol (HTTP) as a transport and extensible markup language (XML) as a data format.

23. A compiler in accordance with claim 17, wherein said web services compatible instructions are compatible with a web services description language (WSDL)-like language.

24. A compiler in accordance with claim 17, wherein said web services compatible instructions are compatible with a simple object oriented protocol (SOAP)-like language.

25. A compiler in accordance with claim 17, wherein said asynchronous transactional messaging language is an XLANG/s-like language.

26. A computer readable storage medium encoded with a computer program code for directing a computer processor to transform instructions in an asynchronous transactional messaging language to instructions compatible with web services, said program code comprising:

a translate proxy class code segment for causing said computer processor to iteratively translate, a predetermined number of times, proxy class instructions of said asynchronous transactional messaging language into corresponding port type instructions compatible with said web services, wherein said predetermined number is determined in accordance with a level of dependency of variables within said asynchronous transactional messaging language;

a translate method code segment for causing said computer processor to translate methods of said proxy class instructions into corresponding operations of said port types;

a translate input parameter code segment for causing said computer processor to translate input parameters of said methods into corresponding request message types of said operations;

a translate output parameter code segment for causing said computer processor to translate output parameters of said methods into corresponding response message types of said operations; and

a store code segment for causing said computer processor to store the translated output parameters.

27. A computer readable storage medium in accordance with claim 26, wherein said web services compatible instructions are compatible with a remote procedure call protocol.

28. A computer readable storage medium in accordance with claim 27, wherein said remote procedure call protocol utilizes hypertext transport protocol (HTTP) as a transport and extensible markup language (XML) as a data format.

29. A computer readable storage medium in accordance with claim 26, wherein said web services compatible instructions are compatible with a web services description language (WSDL).

30. A computer readable storage medium in accordance with claim 26, wherein said web services compatible instructions are compatible with a simple object oriented protocol (SOAP).

31. A computer readable storage medium in accordance with claim 26, wherein said asynchronous transactional messaging is XLANG/s.

32. A computer readable storage medium in accordance with claim 26, further comprising:

an extract method code segment for causing said computer processor to extract a fully qualified method name from a name space of said method;

an append message type code segment for causing said computer processor to append a prefix to said fully qualified method name, said prefix comprising double underscores followed by a term “

messagetype”

followed by a single underscore;

an append suffix code segment for causing said computer processor to appending a suffix to said fully qualified method name, wherein;

if said method comprises an input parameter, said suffix comprises a single underscore followed by a term “

request”

; and

if said method comprises an output parameter, said suffix comprises a single underscore followed by a term “

response”

; and

a second replace code segment for causing said computer processor to replace all periods in said fully qualified method-type name with a single underscore.