US6434628B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Common interface for handling exception interface name with additional prefix and suffix for handling exceptions in environment services patterns
Assignee: Accenture Global Services Ltd
•
Filing: 1999-08-31
•
Granted: 2002-08-13
•
Expires: 2019-08-31
Abstract
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.
Inventors
- 👤 Michel K. Bowman-Amuah
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-25 04:07
CPC Classifications
H; H04; H04L; H04L67/00; H04L67/50; H04L67/56; H04L67/568; H04L9/00; H04L9/40; H04L67/01; H04L69/00; H04L69/30; H04L69/32; H04L69/322; H04L69/329
Claims Analysis
Total Claims: 18
Claim 1
Independent Claim
95 words
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.
Claim 2
Independent Claim
95 words
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.
Claim 3
Dependent Claim
36 words
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.
Claim 4
Dependent Claim
43 words
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.
Claim 5
Dependent Claim
37 words
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.
Claim 6
Dependent Claim
24 words
A method as recited in claim 1 , wherein arbitrary exceptions each support a clone method which creates a copy of the arbitrary exception.
Claim 7
Dependent Claim
127 words
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.
Claim 8
Dependent Claim
127 words
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.
Claim 9
Dependent Claim
38 words
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.
Claim 10
Dependent Claim
45 words
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.
Claim 11
Dependent Claim
39 words
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.
Claim 12
Dependent Claim
26 words
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.
Claim 13
Independent Claim
106 words
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.
Claim 14
Independent Claim
106 words
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.
Claim 15
Dependent Claim
35 words
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.
Claim 16
Dependent Claim
42 words
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.
Claim 17
Dependent Claim
36 words
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.
Claim 18
Dependent Claim
24 words
A system as recited in claim 11 , wherein arbitrary exceptions each support a clone system which creates a copy of the arbitrary exception.
References Cited (Backward Citations)
US5301320A
Cited
US5732270A
Cited
US5907704A
Cited
US5721908A
Cited
US5890133A
Cited
US5953707A
Cited
US5787413A
Cited
US5987514A
Cited
WO1999008208A1
Cited
US6085198A
Cited
US6182182B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-08-12 | 2006-02-11 | 2006-08-13 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-08-12 | 2010-02-11 | 2010-08-13 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-08-12 | 2014-02-11 | 2014-08-13 | $7700.00 | Window Closed / Lapsed |