Methods and apparatus for persisting objects to a database are disclosed. A set of meta-level objects (120) are defined, each object also having defined a persistence strategy. Each object also has a set of attributes which have their own respective persistence strategy. An object also can have an association with other objects each carrying respective persistence and attribute definitions. Upon a persistence request occurring, a run-time instance of an object is created carrying attributes and attached persistence strategies. The instantiated object is then executed. By defining objects, attributes and persistence strategies at a meta-level that only are populated at run-time, they each are able to be readily modified to give effect to a desired change in persistence strategy, including which attributes are to be persisted.

Method and system for recovering information from open files during a failure in a program module. Once a failure is detected in the program module, control passes to an exception handler that determines whether the open files have been modified. If so, the open files are verified and stored as recovery versions of the files at the time of the failure. The program module is then terminated and restarted. Upon restarting the program module, the recovery version of the file at the time of the failure is opened and displayed to the user.

In one embodiment, a method is contemplated. A first parameterization is generated, which describes a desired result in at least a first dimension of a plurality of dimensions of a protection system. The first parameterization is evaluated over a plurality of parameterizations. Each of the plurality of parameterizations corresponds to a respective one of a plurality of instances of a second dimension of the plurality of dimensions. A computer readable medium comprising instructions that implement the method and a system implementing the method are also contemplated.

A system and method for protecting software components of a software system can be used to guard against faults which might occur during the execution of a software component. A software component which is particularly prone to faults may be designated for protection. Faults occurring during execution of these protected software components can be detected, execution of the protected software component can be halted, and the software system may be restored to the state it held before execution of the protected software component commenced. The software system can then resume executing in a normal manner. Furthermore, a default value for the protected software component may be assigned in the event that a fault is detected during execution of the protected software component.

In one embodiment, a method is contemplated. The method includes exposing at least three dimensions of a protection system to a user. The three dimensions are interrelated. The method further includes receiving user input indicating a modification in a first dimension of the at least three dimensions; and determining an effect of the modification in each other dimension of the at least three dimensions. A computer accessible medium comprising a plurality of instructions which, when executed, implement the method and a system implementing the method are also contemplated.