net.rim.device.api.util
Interface Persistable

All Superinterfaces:

net.rim.vm.Persistable

All Known Subinterfaces:

Certificate, CryptoSystem, DHKey, DistinguishedName, DSAKey, ECKey, KEAKey, Key, KeyStoreData, PrivateKey, PublicKey, RSAKey, SymmetricKey

All Known Implementing Classes:

BigIntVector, BigLongVector, BigVector, CodeSigningKey, ControlledAccess, PersistentObject, PersistentStore, SparseList, StringMatch, ToIntHashtable, MultiMap, LongIntHashtable, LongHashtable, IntVector, IntMultiMap, IntIntHashtable, IntHashtable, DataBuffer, ByteVector, ASN1BitSet, CertificateStatus, CertificateServers, CertificateServerInfo, CertificateExtension, TripleDESKey, SkipjackKey, RSAPublicKey, RSAPrivateKey, KeyPair, RSAKeyPair, RSACryptoSystem, RC5Key, RC2Key, KEAPublicKey, KEAPrivateKey, KEAKeyPair, KEACryptoSystem, InitializationVector, HMACKey, ECPublicKey, ECPrivateKey, ECKeyPair, ECCryptoSystem, DSAPublicKey, DSAPrivateKey, DSAKeyPair, DHPublicKey, DHPrivateKey, DHKeyPair, DESKey, CAST128Key, ARC4Key, AESKey, AssociatedData, OID, X509DistinguishedName, X509Certificate, WTLSDistinguishedName, WTLSCertificate

public interface Persistable

extends net.rim.vm.Persistable

Every object that can persist between device resets must implement persistable.

If you want a class to remain compatibile with old instances that are in the persistent store, you can do anything as long as it does not change the instance data layout. So you can do anything at all to the methods and static data. You could change the superclass, as long as the new superclass has all the same instance data (eg: you could insert a class into the hierarchy that had no instance data). What you can't do is add, delete or modify any instance data of the class or its superclasses.