Web services message processing runtime framework

• US 7,788,338 B2
• Filed: 09/21/2005
• Issued: 08/31/2010
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Savchenko, Vladimir S., Angelov, Dimitar
• Primary Examiner(s): Avellino; Joseph E
• Assistant Examiner(s): SHAW, PETER C
• Application Number:
  US11/233,241
• Publication Number:
  US 20070064680A1
• Time in Patent Office: 1,805 Days
• Field of Search: 709/218, 709/202, 709/201, 709/219, 719/313, 719/316
• US Class Current: 709/218
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A method is described that involves processing a Web services message within an object oriented runtime environment. The processing involves executing a plurality of protocols to support a Web service that the message pertains to. Each one of the protocols perform one or more operations that contribute to a different part of the processing. The executing is hibernated by storing state information of the protocols externally from the protocols. The executing is resumed by loading the saved state information back into the protocols. The processing also involves identifying a message key within the message and using the message key to identify an endpoint method for the message. The method also involves executing the endpoint method to generate a response message to the message.

Claims

1. A method, comprising:

reading program code from memory and processing said program code with one or more processors to perform the following method;

processing a Web services message within an object oriented runtime environment, said Web services message having a header portion and a body portion, said header portion and said body portion each formatted according to a Web Services (WS) standard format, said processing comprising;

executing a plurality of stateless protocols to support a Web service that said Web services message is directed to, said stateless protocols operating on said header portion of said Web services message, at least one of said stateless protocols not being a networking protocol, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing of said stateless protocols including storing state information of said protocols externally from said protocols;

identifying a message key within said Web services message and using said message key to identify an endpoint method for said Web services message;

generating an input parameter for said endpoint method, including;

identifying said input parameter by analyzing a classloader for a software component that provides said endpoint method;

analyzing said message for an element containing a value to assign to said input parameter; and

assigning said value to said input parameter; and

executing said endpoint method to generate a response message to said Web services message.

2. The method of claim 1 wherein said method is executed at a Web services provider.

3. The method of claim 1 wherein said method is executed at a Web services consumer.

4. The method of claim 1 wherein said endpoint method is identified by referring to data maintained for said Web service that correlates message keys of messages supported by said Web service to endpoint methods performed by said Web service.

5. An article of manufacture including program code stored on a machine readable storage medium which, when read from memory and executed by one or more processors, causes the machine to perform a method, the method, comprising:

processing a Web services message within an object oriented runtime environment, said Web services message having a header portion and a body portion, said header portion and said body portion each formatted according to a Web Services (WS) standard format, said processing comprising;

executing a plurality of stateless protocols to support a Web service that said Web services message is directed to, said stateless protocols operating on said header portion of said Web services message, at least one of said stateless protocols not being a networking protocol, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing of said stateless protocols including storing state information of said protocols externally from said protocols;

identifying a message key within said Web services message and using said message key to identify an endpoint method for said Web services message;

generating an input parameter for said endpoint method, including;

identifying said input parameter by analyzing a classloader for a software component that provides said endpoint method;

analyzing said message for an element containing a value to assign to said input parameter; and

assigning said value to said input parameter; and

executing said endpoint method to generate a response message to said Web services message.

6. The article of manufacture of claim 5 wherein said method is executed at a Web services provider.

7. The article of manufacture of claim 5 wherein said method is executed at a Web services consumer.

8. The article of manufacture of claim 5 wherein said endpoint method is identified by referring to data maintained for said Web service that correlates message keys of messages supported by said Web service to endpoint methods performed by said Web service.

9. A computing system comprising one or more processors, said computing system also comprising instructions disposed on a computer readable storage medium, said instructions capable of being executed by said one or more processors to perform a method, said method, comprising:

processing a Web services message within an object oriented runtime environment, said Web services message having a header portion and a body portion, said header portion and said body portion each formatted according to a Web Services (WS) standard format, said processing comprising;

executing a plurality of stateless protocols to support a Web service that said Web services message is directed to, said stateless protocols operating on said header portion of said Web services message, at least one of said stateless protocols not being a networking protocol, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing of said stateless protocols including storing state information of said protocols externally from said protocols;

identifying a message key within said Web services message and using said message key to identify an endpoint method for said Web services message;

generating an input parameter for said endpoint method, including;

identifying said input parameter by analyzing a classloader for a software component that provides said endpoint method;

analyzing said message for an element containing a value to assign to said input parameter; and

assigning said value to said input parameter; and

executing said endpoint method to generate a response message to said Web services message.

10. The computing system of claim 9 wherein said method is executed at a Web services provider.

11. The computing system of claim 9 wherein said method is executed at a Web services consumer.