Hello,
I have a change in behavior after updating to MAF 2.2.0. I'm not quite sure if it is intentional or a bug. To me, it seems like a bug because it contradicts the singleton design pattern and the change in behavior only happens once the app is deactivated and then activated again.
Basically, I have a class in the ApplicationController which was implementing the singleton design pattern. The instance of that class (the singleton) behaves like a singleton and is used by all features. Up to MAF 2.1.3, that worked fine. As of MAF 2.2.0, the instance behaves as a singleton until the app is deactivated and then activated again.
Here is the scenario:
1) start the app => the singleton is created
2) go to any feature => the singleton is still the same instance.
3) deactivate the app
4) activate the app
5) The original instance (the singleton) is still available in the ApplicationLifeCycleListenerImpl as we as the feature that the app was in when it was deactivated and activated
6) Go to any other feature => now i have a new instance of the class implementing the singleton pattern (I basically have more than one instance)
Has anybody experienced anything of that sort? I am running on iOS.
Regards,
Majdi Jaqaman