Object Deletion Mechanism Usage Guidelines

The following guidelines describe possible scenarios when the object deletion mechanism might or might not be used:

• When throwing exceptions, avoid creating new exception objects and relying on the object deletion mechanism to perform cleanup. Try to use existing exception objects.

• Try not to create objects in method or block scope. This is acceptable in standard Java technology applications, but is an incorrect use of the object deletion mechanism in Java Card technology-based applications.

• Use the object deletion mechanism when a large object, such as a certificate or key, must be replaced with a new one. In this case, instead of updating the old object in a transaction, create a new object and update its pointer within the transaction. Then, use the object deletion mechanism to remove the old object.

• Use the object deletion mechanism when object resizing is required, as shown in the example in Requesting the Object Deletion Mechanism.