Using a Fragment to retain object instances on device configuration changes - Android

DataFrament.java

/*
 *  Created on base of this tutorial:
 *  http://developer.android.com/guide/topics/resources/runtime-changes.html#RetainingAnObject
 *  Licensed under Apache License 2.0, as the Official Android Documentation
 *
 */

package com.example.myapplication.util;

import android.app.Fragment;
import android.os.Bundle;

/**
 * This class makes preserving object instances on configuration change easy
 * @param <T> Generic type of the object
 */
public class DataFragment<T> extends Fragment {

    private T data;

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setRetainInstance(true);
    }

    public void setData(T data) { this.data = data; }

    public T getData() { return data; }

}

An important note from documentation:

Caution: While you can store any object, you should never pass an object that is tied to the Activity, such as a Drawable, an Adapter, a View or any other object that's associated with a Context. If you do, it will leak all the views and resources of the original activity instance. (Leaking resources means that your application maintains a hold on them and they cannot be garbage-collected, so lots of memory can be lost.)