Common interface for handling exception interface name with additional prefix and suffix for handling exceptions in environment services patterns

• US 6,434,628 B1
• Filed: 08/31/1999
• Issued: 08/13/2002
• Est. Priority Date: 08/31/1999
• Status: Expired due to Term

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Bowman-Amuah, Michel K.
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US09/386,434
• Time in Patent Office: 1,078 Days
• Field of Search: 709/303, 709/224, 714/1, 714/15, 714/48
• US Class Current: 714/48
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system, method and article of manufacture are provided for creating a common interface for exception handling. Naming conventions of exceptions are determined. A prefix and/or a suffix is added to each exception interface name for indicating that the exception interface is an exception. Where an exception error occurred is indicated and a determination is made as to what caused the exception error. Context is provided as to what was happening when the exception error occurred. Streaming of the exception is allowed to a common interface. An error message is outputted indicating that an exception error has occurred.

Claims

1. A method for creating a common interface for exception handling, comprising the steps of:

(a) determining naming conventions of exceptions;

(b) adding at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception;

(c) indicating where an exception error occurred;

(d) determining what caused the exception error;

(e) providing context as to what was happening when the exception error occurred;

(f) allowing streaming of the exception to a common interface; and

(g) outputting an error message indicating that an exception error has occurred.

2. A method as recited in claim 1, further comprising the step of adding at least one of a layer and domain from which each exception originates to each of the names of the exception interfaces.

3. A method as recited in claim 1, further comprising the step of partitioning the exceptions into classes based on at least one of the way exceptions are handled, exceptions associated with different layers of a system, domains, and source of the exceptions.

4. A method as recited in claim 1, further comprising the step of creating a class which represents a source of the exception and holds an original copy of the exception for avoiding creation of duplicate exceptions.

5. A method as recited in claim 1, wherein arbitrary exceptions each support a clone method which creates a copy of the arbitrary exception.

6. A computer program embodied on a computer readable medium for creating a common interface for exception handling, comprising:

(a) a code segment that determines naming conventions of exceptions;

(b) a code segment that adds at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception;

(c) a code segment that indicates where an exception error occurred;

(d) a code segment that determines what caused the exception error;

(e) a code segment that provides context as to what was happening when the exception error occurred;

(f) a code segment that allows streaming of the exception to a common interface; and

(g) a code segment that outputs an error message indicating that an exception error has occurred.

7. A computer program as recited in claim 6, further comprising a code segment that adds at least one of a layer and domain from which each exception originates to each of the names of the exception interfaces.

8. A computer program as recited in claim 6, further comprising a code segment that partitions the exceptions into classes based on at least one of the way exceptions are handled, exceptions associated with different layers of a system, domains, and source of the exceptions.

9. A computer program as recited in claim 6, further comprising a code segment that creates a class which represents a source of the exception and holds an original copy of the exception for avoiding creation of duplicate exceptions.

10. A computer program as recited in claim 6, wherein arbitrary exceptions each support a clone computer program which creates a copy of the arbitrary exception.

11. A system for creating a common interface for exception handling, comprising:

(a) logic that determines naming conventions of exceptions;

(b) logic that adds at least one of a prefix and a suffix to each exception interface name for indicating that the exception interface is an exception;

(c) logic that indicates where an exception error occurred;

(d) logic that determines what caused the exception error;

(e) logic that provides context as to what was happening when the exception error occurred;

(f) logic that allows streaming of the exception to a common interface; and

(g) logic that outputs an error message indicating that an exception error has occurred.

12. A system as recited in claim 11, further comprising logic that adds at least one of a layer and domain from which each exception originates to each of the names of the exception interfaces.

13. A system as recited in claim 11, further comprising logic that partitions the exceptions into classes based on at least one of the way exceptions are handled, exceptions associated with different layers of a system, domains, and source of the exceptions.

14. A system as recited in claim 11, further comprising logic that creates a class which represents a source of the exception and holds an original copy of the exception for avoiding creation of duplicate exceptions.

15. A system as recited in claim 11, wherein arbitrary exceptions each support a clone system which creates a copy of the arbitrary exception.