Annotation based development platform for asynchronous web services

• US 7,356,803 B2
• Filed: 02/22/2002
• Issued: 04/08/2008
• Est. Priority Date: 07/02/2001
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bosworth, Adam, Marvin, Kyle W., Chavez, Roderick A., Bau, David III, Burd, Gary S.
• Primary Examiner(s): Thomson; William
• Assistant Examiner(s): Hoang; Phuong N
• Application Number:
  US10/082,807
• Publication Number:
  US 20030005181A1
• Time in Patent Office: 2,237 Days
• Field of Search: 717116-117, 717/140, 717/136, 717/137, 717/143, 719/311, 719/315, 719/330
• US Class Current: 717/116
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06F 8/447 Target code generation

Abstract

An annotation based development platform for asynchronous web services is described. In one embodiment, the developer expresses logic offered by the web service using a standard programming language augmented with declarative annotations specifying preferences for exposing that logic as an asynchronous web service. At compile time, an enhanced compiler analyzes the annotated source file and automatically generates the mechanisms required to expose its functionality as an asynchronous web service.

Claims

1. In a server having an asynchronous web service, a method comprising:

receiving by the server a message from a client remotely disposed from the server requesting that the web service be invoked;

parsing by the server the message to identify the requested web service method in addition to a callback address indicating a location where the client is listening for callbacks from the web service;

storing by the server the callback address in association with a proxy object; and

invoking by the server the requested web service method, including passing programming language objects as parameters to the web service method, the programming language objects having been mapped from data representation language elements of the message.

2. The method of claim 1, further comprising:

identifying an instance identifier provided by the client indicating a particular instance of the client that is listening for callbacks from the web service; and

storing the instance identifier in association with the callback address and the proxy object.

3. The method of claim 2, wherein at least one of the callback address and the instance identifier is encapsulated in one or more request messages.

4. The method of claim 3, wherein at least one of the callback address and the instance identifier is encapsulated in one or more SOAP message headers.

5. The method of claim 2, wherein the instance identifier is embedded within a conversation identifier used to access a corresponding instance of a conversation between the client and the web service.

6. The method of claim 2, wherein the instance identifier is a GUID.

7. The method of claim 2, further comprising:

generating an asynchronous response to the client in response to the message by invoking a method on the proxy object using a declared member variable, wherein invoking includes passing programming language objects as parameters to said method,

mapping the programming language objects and method invocation onto representative data representation language elements;

packaging the representative data representation language elements, and callback instance identifier into an asynchronous response message; and

transmitting the asynchronous response message to the client at the callback address in accordance with one or more protocols used by the client in transmitting the original request message to the web service.

8. The method of claim 1, wherein invoking the requested web service method further comprises:

mapping programming language objects returned by the web service method onto representative data representation language elements;

packaging the representative data representation language elements according to one or more protocols used by the client in generating the requested message; and

transmitting the packaged data representation elements to the client in accordance with one or more protocols used by the client in transmitting the message to the web service.

9. An article of manufacture comprising:

a storage medium having stored therein a plurality of programming instructions designed to program a server to implement an asynchronous web service, which programming instructions when executed enable the server to

receive a message from a client requesting that a web service method be invoked;

parse the message to identify the requested web service method in addition to a callback address indicating a location where the client is listening for callbacks from the web service;

store the callback address in association with a proxy object; and

invoke the requested web service method, including passing programming language objects as parameters to the web service method, the programming language objects having been mapped from data representation language elements of the message.

10. The article of claim 9, wherein the programming instructions further enable the server to

identify an instance identifier provided by the client indicating a particular instance of the client that is listening for callbacks from the web service;

and

store the instance identifier in association with the callback address and the proxy object.

11. The article of claim 10, wherein at least one of the callback address and the instance identifier is encapsulated in one or more request messages.

12. The article of claim 11, wherein at least one of the callback address and the instance identifier is encapsulated in one or more SOAP message headers.

13. The article of claim 10, wherein the instance identifier is embedded within a conversation identifier used to access a corresponding instance of a conversation between the client and the web service.

14. The article of claim 10, wherein the instance identifier is a GUID.

15. The article of claim 10, wherein the programming instructions further enable the server to generate an asynchronous response to the client in response to the message by invoking a method on the proxy object using a declared member variable, wherein invoking includes

passing programming language objects as parameters to said method,

mapping the programming language objects and method invocation onto representative data representation language elements;

packaging the representative data representation language elements, and callback instance identifier into an asynchronous response message, and

transmitting the asynchronous response message to the client at the callback address in accordance with one or more protocols used by the client in transmitting the original request message to the web service.

16. The article of claim 9, wherein the programming instructions to cause the server to invoke the requested web service further cause the server to

map programming language objects returned by the web service method onto representative data representation language elements;

package the representative data representation language elements according to one or more protocols used by the client in generating the requested message; and

transmit the packaged data representation elements to the client in accordance with one or more protocols used by the client in transmitting the message to the web service.