System and method for callbacks based on web service addressing

• US 8,484,281 B2
• Filed: 08/20/2012
• Issued: 07/09/2013
• Est. Priority Date: 01/11/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jin, Lei, Zotter, Brian
• Primary Examiner(s): NGUYEN, THU HA T
• Application Number:
  US13/589,296
• Publication Number:
  US 20120311018A1
• Time in Patent Office: 323 Days
• Field of Search: 709/200, 709/206, 709/207, 709/217, 370/260
• US Class Current: 709/202
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

Embodiments of the present invention enable related parties to setup asynchronous messaging exchanges between Web services based on Web service addressing. All the callback address lookup, population and setup can be performed automatically by the service provider at the infrastructure level transparent to the user and only the service/contract itself need to be defined. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system to provide a conversational service through callbacks via Web service addressing, comprising:

a first client operable to;

implement a contract for the conversational service by compiling a software component in accordance with the contract;

submit a conversational service request to the service provider via Web service addressing, the conversational service request containing a callback address of the first client in a header of the conversational service request, wherein the callback address is associated with a conversation identification adapted for the service provider to notify the first client; and

accept a response associated with the conversation identification; and

said service provider operable to;

define the conversational service as the contract based on the Web service addressing;

process the conversational service request from the first client;

obtain the callback address of the first client from the header of the conversational service request;

populate the callback address of the first client to a callback stub;

automatically invoke the callback stub when the response from the conversational service is available; and

provide the response associated with the conversation identification to the first client.

2. The system according to claim 1, wherein the Web service addressing can be WS-Addressing.

3. The system according to claim 1, wherein the first client is a Web service.

4. The system according to claim 1, wherein the service provider is operable to extract the address of the first client from the header of the conversational service request.

5. The system according to claim 1, wherein the conversational service is asynchronous.

6. The system according to claim 5, wherein the conversational service provider is operable to wait for the response from the conversational service becomes available before invoking the callback stub.

7. The system according to claim 5, wherein the callback stub can be reused over time once initialized.

8. The system according to claim 1, wherein the software component is a stub.

9. The system according to claim 1, wherein the callback stub can be included as a parameter in the service request under a non-conversational scenario or kept as part of a conversational state on the service provider under a conversational scenario.

18. The system of claim 1, wherein the first client proposes the conversation identification.

19. The system of claim 1, further comprising:

a second client operable to;

accept the conversation identification from the service provider; and

participate in the conversational service by embedding the conversation identification in communication with the service provider.

10. A method to provide a conversational service through callbacks via Web service addressing, comprising:

defining the conversational service as a contract;

implementing the contract by compiling a software component in accordance with the contract;

submitting a conversational service request from a first client to a service provider via Web service addressing, the conversational service request containing a callback address of the first client in a header of the conversational service request, wherein the callback address is associated with a conversation identification adapted for the service provider to notify the first client;

processing the conversational service request to obtain the callback address of the first client from the header of the conversational service request;

populating the callback address of the first client to a callback stub; and

automatically invoking the callback stub when a response from the conversational service is available;

providing the response associated with the conversation identification to the first client.

11. The method according to claim 10, further comprising:

extracting the callback address of the first client from the header of the service request.

12. The method according to claim 10, wherein the conversational service is asynchronous.

13. The system according to claim 12, further comprising:

waiting for the response from the conversational service becomes available before invoking the callback stub.

14. The system according to claim 12, further comprising:

reusing the callback stub over time once initialized.

15. The method according to claim 10, wherein the software component is a stub.

16. The method according to claim 15, further comprising:

including the callback stub as a parameter in the service request under a non-conversational scenario or keeping it as part of a conversational state on the service provider under a conversational scenario.

20. The method of claim 10, further comprising:

sending the conversation identification to a second client;

receiving the response from the second client by embedding the conversation identification in communication with the second client.

17. A non-transitory machine readable medium comprising instructions stored thereon that when executed cause a system to:

define a contract for a conversational service based on a web service addressing protocol;

implement the contract by compiling a software component in accordance with the contract;

submit a conversational service request from a first client to a service provider for the conversational service via Web service addressing, the conversational service request containing a callback address of the first client in a header of the conversational service request, wherein the callback address is associated with a conversation identification adapted for the service provider to notify the first client;

process the conversational service request to obtain the callback address of the first client from the header of the conversational service request;

populate the callback address of the first client to a callback stub; and

invoke the callback stub when a response from the conversational service is available;

provide the response associated with the conversation identification to the first client.