System and method for web services Java API-based invocation

• US 7,769,825 B2
• Filed: 06/26/2003
• Issued: 08/03/2010
• Est. Priority Date: 02/22/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Ferguson, Don, Cheenath, Manoj, Karakashian, Todd
• Primary Examiner(s): SHAW, PELING ANDY
• Application Number:
  US10/606,573
• Publication Number:
  US 20040064503A1
• Time in Patent Office: 2,595 Days
• Field of Search: 709202-203, 709/217, 709/219, 709/227, 709/230, 379/201.03, 707/103, 707/3, 707/10, 719/315, 719330-332, 717/149
• US Class Current: 709/219
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A runtime architecture for web services utilizes a container driver to accept an invoke request for web services, such as from a protocol adapter. The container driver performs any necessary data binding and unbinding required to process the invoke request and associated message context, utilizing an appropriate plugin component. An interceptor receives the context information from the container driver and modifies the message context for web service compatibility. An invocation handler receives the formatted context information from the container driver and passes parameters from the message context to the target of the request. The invocation handler processes values returned from the target and passes these values to the container driver. The container driver can then formulate a response to the invoke request, and return the response and message context to the client or protocol adapter.

Claims

1. A storage medium including software system applications for providing access to web services, comprising:

a protocol adapter that

intercepts a web service invoke request wherein the invoke request is a web service message that has a message format and includes parameters,

converts the message format of the invoke request,

creates an initial message context including the invoke request, a placeholder for a response, and information about a transport, and

routes the invoke request with the initial message context to an appropriate web services container based on a target of the invoke request;

a container driver, at the web services container, that receives the invoke request and initial message context from the protocol adapter;

a plurality of interceptors, utilized by the container driver to access inbound and outbound web service messages;

wherein the container driver forwards the initial message context to one of the plurality of interceptors that

receives the initial message context which includes a plurality of parts, wherein each part includes corresponding content,

modifies the content of one or more of the parts of the initial message context to produce modified message context, and

returns the modified message context to the container driver;

an invocation handler that receives the modified message context from said container driver, passes the parameters from the modified message context to the target of the request, processes values returned from the target, and passes the values to the container driver, such that the container driver can formulate a response to the invoke request; and

an invocation context that stores context data for processing the invoke request including a conversation ID, a message sequence number, and a security token, wherein the invocation context is an inheritable, thread local object which is accessible to the protocol adapter, interceptors and invocation handler, and wherein the invocation handler controls read/write access to the invocation context.

2. The storage medium of claim 1 wherein the client utilizes JAX-RPC to invoke the web services.

3. The storage medium of claim 1 wherein said container driver is adapted to perform any data binding and unbinding required to process the invoke request.

4. The storage medium of claim 1, further comprising a plugin component to be used by said container driver to perform any data binding and unbinding.

5. The storage medium of claim 1, wherein said invocation handler manages security policies, transaction management, and target object life cycle for the request.

6. The storage medium of claim 1, further comprising a web service container for hosting said container driver, said interceptor, and said invocation handler.

7. The storage medium of claim 1, further comprising a target object to which said invocation handler can delegate processing the invoke request.

16. The storage medium of claim 1, wherein the plurality of parts for the initial message context and the plurality of parts for the modified message context each include a request message and a response message with a difference between the initial message context and the modified message context being the content of one or more of these parts.

17. The storage medium of claim 1, wherein the interceptor reads and writes information on the invocation context.

18. The storage medium of claim 1, wherein the initial message context and the modified message context each include transport information, wherein the transport information comprises information specific to the transport over which the request came, and over which the response is sent.

19. The storage medium of claim 1 wherein the protocol adapter receives data in response to the invoke request and returns the data to the client.

20. The storage medium of claim 19 wherein the protocol adapter converts a message format of the data in response to the invoke request to match the message format of the invoke request.

8. A method for use in providing access to web services, comprising:

intercepting at a web server computer a web service invoke request using a protocol adapter, wherein the invoke request is a web service message having a message format and where the invoke request includes parameters;

converting the message format of the invoke request by the protocol adapter;

creating an initial message context including the invoke request, a placeholder for a response, and information about a transport;

routes the invoke request with the initial message context to an appropriate web services container based on a target of the invoke request;

receiving, at a container driver, the invoke request and the initial message context from the protocol adapter;

forwarding the initial message context for the invoke request for a web service to one of a plurality of interceptors, wherein the plurality of interceptors are utilized by the container driver to access inbound and outbound web service message, and wherein the initial message context includes a plurality of parts, wherein each part includes corresponding content;

modifying the content of one or more of the parts of the initial message context to produce modified message context;

returning the modified message content to the container driver;

receiving the modified message context from the container driver at an invocation handler, wherein the invocation handler

passes the parameters from the modified message context to the target of the request,

processes values returned from the target, and

passes the values to the container driver such that the container driver can formulate a response to the invoke request;

storing, in an invocation context, context data for processing the invoke request including a conversation ID, a message sequence number, and a security token, wherein the invocation context is an inheritable, thread local object which is accessible to the protocol adapter, interceptors and invocation handler, and wherein an invocation handler controls read/write access to the invocation context.

9. The method of claim 8 wherein a client utilizes JAX-RPC to invoke the web service.

10. The method of claim 8 wherein a container driver is used to perform any data binding and unbinding required to process the invoke request.

11. The method of claim 8, wherein the receiving and modifying steps are performed using an interceptor.

12. The method of claim 8, further comprising providing the modified message context to the invocation handler that passes parameters from the modified message context to a target of the request, processes values returned from the target, and passes the values to a container driver, such that the container driver can formulate a response to the invoke request.

13. The method of claim 8, further comprising managing life cycle, transaction, and security information for the processing of the invoke request.

14. The method of claim 8, further comprising delegating the processing of the invoke request to a target object.

21. The method of claim 8 wherein the protocol adapter receives data in response to the invoke request and returns the data to the client.

22. The method of claim 21 wherein the protocol adapter converts a message format of the data in response to the invoke request to match the message format of the invoke request.

15. A computer readable medium, including instructions stored thereon which when executed by the computer cause the computer to perform the steps of:

intercepting a web service invoke request using a protocol adapter, wherein the invoke request is a web service message having a message format and wherein the invoke request includes parameters;

converting the message format of the invoke request by the protocol adapter;

creating an initial message context including the invoke request, a placeholder for a response, and information about a transport;

routes the invoke request with the initial message context to an appropriate web services container based on a target of the invoke request;

receiving, at a container driver, the invoke request and the initial message context from the protocol adapter;

forwarding the initial message context for the invoke request for the web service from the container driver to one of a plurality of interceptors, wherein the plurality of interceptors are utilized by the container driver to access inbound and outbound web service message, and wherein the initial message context includes a plurality of parts, wherein each part includes corresponding content;

modifying, at the interceptor, the content of one or more of the parts of the initial message context to produce modified message context for the web service;

returning the modified message content to the container driver;

receiving, at an invocation handler, the modified message context from the container driver, wherein the invocation handler

passes the parameters from the modified message context to the target of the request,

processes values returned from the target, and

passes the values to the container driver such that the container driver can formulate a response to the invoke request;

storing, at an invocation context, context data for processing the invoke request including a conversation ID, a message sequence number, and a security token, wherein the invocation context is an inheritable, thread local object which is accessible to the protocol adapter, interceptors and invocation handle, and wherein the invocation handler controls read/write access to the invocation context;

passing, from the invocation handler to a target of the request, parameters from the modified message context;

processing, at the invocation handler, values returned from the target;

passing the values from the invocation handler to the container driver; and

formulating, at the container driver, a response to the invoke request.

23. A storage medium including software system applications for providing access to web services, comprising:

a protocol adapter that

intercepts a web service invoke request wherein the invoke request is a web service message that has a message format and includes parameters,

converts the message format of the invoke request,

creates an initial message context including the invoke request, a placeholder for a response, and information about a transport, and

routes the invoke request with the initial message context to an appropriate web services container based on a target of the invoke request;

a container driver, at the web services container, that receives the invoke request and initial message context from the protocol adapter;

a plurality of interceptors, utilized by the container driver to access inbound and outbound web service messages;

wherein the container driver forwards the initial message context to one of the plurality of interceptors that

receives the initial message context which includes a plurality of parts, wherein each part includes corresponding content,

modifies the content of one or more of the parts of the initial message context to produce modified message context, and

returns the modified message context to the container driver;

a plurality of codecs utilized by the container driver to perform data binding;

an invocation handler that receives the modified message context from said container driver, passes the parameters from the modified message context to the target of the request, processes values returned from the target, and passes the values to the container driver, such that the container driver can formulate a response to the invoke request; and

an invocation context that stores context data for processing the invoke request including a conversation ID, a message sequence number, and a security token, wherein the invocation context is an inheritable, thread local object which is accessible to the protocol adapter, interceptors and invocation handler, and wherein the invocation handler controls read/write access to the invocation context.