I have data that must undergo the upheavals and death of the process.

Now I have done data storage in the presenter. And in the presenter I added methods saveInstanceState(bundle state) and restoreInstanceState(Bundle state) . These presenter methods are simply called by the fragment in onSaveInstanceState and onCreate respectively.

But this is bad, because in this way the presenter knows about android sdk classes and it is not possible to test his unit with tests. Well, only if the bundle.
I was offered a solution to wrap the data in a pojo class, i.e. So that the presenter returns a pojo class that, say, Serializable and a fragment, tugged this method of the presenter, got this pojo class and already saved it in a bundle. But in this way I get a twist (fragment) is not very passive.

Maybe someone has already solved a similar problem and knows the best solution?

    1 answer 1

    In general, the approach recommended to you is correct, but more correctly this way:

    1) when turning, the presenter should not die, since this is a purely feature of the android - the dying view

    2) to recover from the death process, do the following
    - bring such data to the Pojo model.
    - in the model make two methods saveToBundle(bundle) and restoreFromBundle(bundle)
    - inject it into classes where it is needed, as well as into the class Activiti
    - to activate save and restore data after the death of the process

    Thus, Activiti will play the role of a system component with the task of recovering data from the death process.

    But it is important to remember that usually storing in a bundle is an extreme measure. All necessary data must be in the database or other storage.