Web services hibernation

• US 20070067383A1
• Filed: 09/21/2005
• Published: 03/22/2007
• Est. Priority Date: 09/21/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Savchenko, Vladimir, Angelov, Dimitar, Baikov, Chavdar
• Granted Patent: US 7,721,293 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level

Abstract

A method is described that involves comprising, during runtime in an object-oriented environment, invoking, from an object, a first Web services endpoint method to process a first message by: invoking the first Web services endpoint method through a first interface according to an endpoint method invocation format, where, the first Web services endpoint method is implemented with a first component that is provided one or more services by a first container. The method also involves invoking, from the object, a second Web services endpoint method to process a second message by: invoking the second Web services endpoint method through a second interface according to the endpoint method invocation format. The second Web services endpoint method is implemented with a second component that is provided one or more services by a second container. The first and second containers have respective interfaces that are different.

Claims

1. A method, comprising:

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing a plurality of protocols to support a Web service that said message pertains to, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing being hibernated by storing state information of said protocols externally from said protocols, said executing being resumed by loading said saved state information back into said protocols;

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

,

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

2. The method of claim 1 further comprising:

invoking, from an object, a Web Services endpoint method to process said message by;

invoking said Web Services endpoint method through a first interface according to an endpoint method invocation format, said Web Services endpoint method implemented with a component that is provided one or more services by a container; and

,

3. The method of claim 2 further comprising processing a second Web services message by

invoking, from said object, a second Web Services endpoint method to process a second message by:

invoking said second Web Services endpoint method through a second interface according to said endpoint method invocation format, said second Web Services endpoint method implemented with a second component that is provided one or more services by a second container, said container and second container having respective interfaces that are different.

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

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

6. The method of claim 1 further comprising generating an input parameter for said endpoint method by:

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

,

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

7. 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.

8. The method of claim 1 wherein said data is cached.

9. An article of manufacture including program code which, when executed by a machine, causes the machine to perform a method, the method, comprising:

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing a plurality of protocols to support a Web service that said message pertains to, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing being hibernated by storing state information of said protocols externally from said protocols, said executing being resumed by loading said saved state information back into said protocols;

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

,

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

10. The article of manufacture of claim 9 further comprising:

invoking, from an object, a Web Services endpoint method to process said message by;

invoking said Web Services endpoint method through a first interface according to an endpoint method invocation format, said Web Services endpoint method implemented with a component that is provided one or more services by a container; and

,

11. The article of manufacture of claim 10 further comprising processing a second Web services message by

invoking, from said object, a second Web Services endpoint method to process a second message by:

invoking said second Web Services endpoint method through a second interface according to said endpoint method invocation format, said second Web Services endpoint method implemented with a second component that is provided one or more services by a second container, said container and second container having respective interfaces that are different.

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

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

14. The article of manufacture of claim 9 further comprising generating an input parameter for said endpoint method by:

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

,

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

15. The article of manufacture of claim 9 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.

16. The article of manufacture of claim 9 wherein said data is cached.

17. A computing system comprising a machine, said computing system also comprising instructions disposed on a computer readable medium, said instructions capable of being executed by said machine to perform a method, said method, comprising:

processing a Web services message within an object oriented runtime environment, said processing comprising;

executing a plurality of protocols to support a Web service that said message pertains to, each one of said protocols performing one or more operations that contribute to a different part of said processing, said executing being hibernated by storing state information of said protocols externally from said protocols, said executing being resumed by loading said saved state information back into said protocols;

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

,

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

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

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

20. The computing system of claim 17 further comprising generating an input parameter for said endpoint method by:

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

,

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