System and method for fault mapping of exceptions across programming models

• US 8,001,424 B2
• Filed: 02/11/2010
• Issued: 08/16/2011
• Est. Priority Date: 06/29/2007
• Status: Expired due to Fees

• Current Assignee: GlobalFoundries, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Allen, Corville O.
• Primary Examiner(s): Maskulinski; Michael C
• Application Number:
  US12/704,464
• Publication Number:
  US 20100146347A1
• Time in Patent Office: 551 Days
• Field of Search: None
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level

Abstract

A system and method for mapping exceptions from a first programming model to a second programming model. The system comprises a first device operating a first programming model and a second device operating a second programming model. The first device sends an instruction to, or invokes the second device to execute an instruction. As a result, a fault occurs during execution of the instruction in the second programming model. An exception based on the fault is raised, and returned to the first device. A fault mapping module receives the exception from the first device. The fault mapping module attempts to determine the type of exception received by comparing an identifier with predetermined identifiers indicating exception type. The fault mapping module interprets the exception to generate an interpreted exception recognizable by the first programming model if the exception is determined to be of a predetermined type.

Claims

1. A computer program product comprising a computer readable storage medium having a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

receive, from a first device operating a first programming model, an exception that includes a set of data and is based upon a fault that occurred during execution of an instruction in a second programming model operating on a second device, the instruction having been transmitted by the first device to the second device;

determine a type of the exception by comparing an identifier associated with the exception with one or more predetermined identifiers that indicate exception type;

determine if the exception is one of a business type exception and a system specific exception; and

interpret the exception according to a set of mapping data to generate an interpreted exception if the exception is determined to be of a predetermined type.

2. The computer program product of claim 1 wherein the first programming model includes a business process execution language.

3. The computer program product of claim 1 wherein the first programming model utilizes a communication protocol that is different from the second programming model.

4. The computer program product of claim 1 wherein the identifier includes a code.

5. The computer program product of claim 1 wherein the set of mapping data is stored in a database.

6. The computer program product of claim 1 wherein the exception is determined to be a business type exception and the business type exception is based on a fault resulting from a violation of a business rule.

7. The computer program product of claim 1 wherein the exception is determined to be a system specific exception type, and the error message is relevant to the system specific exception type.

8. A system comprising:

a first device operating a first programming model;

a second device operating a second programming model, the second device being invoked by the first device to execute an instruction; and

a fault mapping module configured to receive an exception from the first device, the exception based on a fault that occurred during the execution of the instruction in the second programming model, the fault mapping module configured to determine a type of the exception by comparing an identifier within the exception with one or more identifiers indicating a type, wherein the fault mapping module determines if the exception is one of a business type exception and a system specific exception and interprets the exception according to a set of mapping data to generate an interpreted exception if the exception is determined to be of a predetermined type.

9. The system of claim 8 wherein the first programming model includes a business process execution language.

10. The system of claim 8 wherein the fault mapping module is configurable to interpret one or more different types of exceptions.

11. The system of claim 8 wherein the business type exception is based on a fault resulting from a violation of a business rule.

12. The system of claim 8 wherein the fault mapping module returns an error if the type of the exception is an unknown type.

13. A method comprising:

receiving from a first device operating a first programming model, an exception that includes a set of data and is based upon a fault that occurred during execution of an instruction in a second programming model operating on a second device, the instruction having been transmitted by the first device to the second device;

determining a type of the exception by comparing an identifier associated with the exception with one or more predetermined identifiers that indicate exception type;

determining if the exception is one of a business type exception and a system specific exception; and

interpreting the exception according to a set of mapping data to generate an interpreted exception if the exception is determined to be of a predetermined type.

14. The method of claim 13 wherein the first programming model includes a business process execution language.

15. The method of claim 13 wherein the first device and the second device have a client-server relationship.

16. The method of claim 13 wherein the first programming model utilizes a communication protocol that is different from the second programming model.

17. The method of claim 13 wherein the interpreted exception is returned to the first device and handled by the first programming model.

18. The method of claim 13 wherein the business type exception is based on a fault resulting from a violation of a business rule.

19. The method of claim 13 wherein the exception is determined to be a system specific exception type, and the error message is relevant to the system specific exception type.