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

• US 20040255046A1
• Filed: 06/11/2003
• Published: 12/16/2004
• Est. Priority Date: 06/11/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: McCrady, Donald James, Ringseth, Paul F.
• Granted Patent: US 7,194,733 B2
• Time in Patent Office: Days
• US Class Current: 709/246
• 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:

transforming proxy class instructions of said asynchronous transactional messaging language into corresponding port type instructions compatible with said web services;

transforming methods of said proxy class instructions into corresponding operations of said port types;

transforming input parameters of said methods into corresponding request message types of said operations; and

transforming output parameters of said methods into corresponding response message types of said operations.

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 class name from a name space of said proxy class;

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

porttype”

followed by a single underscore; and

replacing all periods in said fully qualified class name with a single underscore.

8. 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 class name with a single underscore.

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

compiling said instructions in said asynchronous transactional messaging language for providing compilation units;

organizing said compilation units into a tree;

traversing said tree in depth first traversal order;

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

10. A method in accordance with claim 9, wherein said act of compiling comprises:

iteratively compiling said first instructions a predetermined number of times, wherein;

said predetermined number is determined in accordance with a level of dependency of variables within said asynchronous transactional messaging language.

11. A method in accordance with claim 10, 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.

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

13. A method in accordance with claim 9, wherein said act of transforming comprises:

upon encountering all types associated with a service, transforming 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, transforming method based messages and class based ports in said asynchronous transactional messaging language with types compatible with said web services.

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

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

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

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

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

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

a code generator for;

compiling said instructions in said asynchronous transactional messaging language for providing compilation units;

organizing said compilation units into a tree; and

traversing said tree in depth first traversal order; and

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

20. A compiler in accordance with claim 19, 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.

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

22. A compiler in accordance with claim 19, 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.

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

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

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

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

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

28. A computer readable 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 transform proxy class code segment for causing said computer processor to transform proxy class instructions of said asynchronous transactional messaging language into corresponding port type instructions compatible with said web services;

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

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

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

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

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

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

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

33. A computer readable medium in accordance with claim 28, wherein said asynchronous transactional messaging is XLANG/s.

34. A computer readable medium in accordance with claim 28, further comprising:

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

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

porttype”

followed by a single underscore; and

a first replace code segment for causing said computer processor to replace all periods in said fully qualified class name with a single underscore.

35. A computer readable medium in accordance with claim 28, 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 replacing all periods in said fully qualified class name with a single underscore.