Error handling for a service oriented architecture

• US 20060005063A1
• Filed: 05/18/2005
• Published: 01/05/2006
• Est. Priority Date: 05/21/2004
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Kasi, Jayaram, Mihic, Matthew, Urhan, Tolga, Kapoor, Chet, Aletty, Ashok, Patrick, Paul B.
• Application Number:
  US11/131,719
• Publication Number:
  US 20060005063A1
• Time in Patent Office: Days
• US Class Current: 714/1
• CPC Class Codes: G06F 11/0772 Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40

Abstract

A system, method and media for a service oriented architecture. 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 method for processing messages for a service proxy, comprising:

providing a message to a first message processing entity in a first scope;

detecting an error in the first message processing entity;

presenting the opportunity to handle the error to the first scope; and

propagating the error to a second scope if the first scope did not handle the error.

2. The method of claim 1 wherein:

the first scope includes a first error handler.

3. The method of claim 1 wherein:

a scope includes at least one of;

a message processing entity and another scope.

4. The method of claim 1 wherein:

the first message processing entity is logically contained within a second message processing entity in the second scope.

5. The method of claim 1 wherein:

a message processing entity is one of;

a message processing stage, a message processing pipeline, a message processing node, and a message processing graph.

6. The method of claim 1 wherein:

the service proxy is an intermediary between a client and one of;

another service proxy and a service.

7. The method of claim 1, further comprising:

responding to the message.

8. The method of claim 1, further comprising:

handling the error in one of;

the first scope and the second scope.

9. The method of claim 1, further comprising:

providing the message to a second message processing entity after the error has been handled.

10. A machine readable medium having instructions stored thereon to cause a system to:

provide a message to a first message processing entity in a first scope;

detect an error in the first message processing entity;

present the opportunity to handle the error to the first scope; and

propagate the error to a second scope if the first scope failed to handle the error.

11. A service proxy for processing messages, comprising:

a first scope including a first message processing entity wherein the first message processing entity is configured to accept a message;

a second scope;

one or more components configured to;

provide a message to a first message processing entity;

detect an error in the first message processing entity;

present the opportunity to handle the error to the first scope; and

propagate the error to the second scope if the first scope failed to handle the error.

12. The service proxy of claim 11 wherein:

the first scope includes a first error handler.

13. The service proxy of claim 11 wherein:

a scope includes at least one of;

a message processing entity and another scope.

14. The service proxy of claim 11 wherein:

the first message processing entity is logically contained within a second message processing entity in the second scope.

15. The service proxy of claim 11 wherein:

a message processing entity is one of;

a message processing stage, a message processing pipeline, a message processing node, and a message processing graph.

16. The service proxy of claim 11 wherein:

the service proxy is an intermediary between a client and one of;

another service proxy and a service.

17. The service proxy of claim 11, wherein the one or more components are further configured to:

respond to the message.

18. The service proxy of claim 11, wherein the one or more components are further configured to:

handle the error in one of;

the first scope and the second scope.

19. The service proxy of claim 11, wherein the one or more components are further configured to:

provide the message to a second message processing entity after the error has been handled.