René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"@EBean(SINGLETON) and getInstance_(Context) on BackgroundThread","articleBody":"When an Activity uses a `@Bean` that it initializes in a background Thread (afaik, there is no other way to avoid just showing the background until after initialization), the code for initializing the bean is not thread safe, and can cause (and for me, causes) Exceptions because the instance exists, but has not received a state yet.\n\nThe following is a typical getInstance_() method:\n\n``` java\n    public static Client_ getInstance_(Context context) {\n        if (instance_ == null) {\n            OnViewChangedNotifier previousNotifier = OnViewChangedNotifier.replaceNotifier(null);\n            instance_ = new Client_(context.getApplicationContext());\n            instance_.init_();\n            OnViewChangedNotifier.replaceNotifier(previousNotifier);\n        }\n        return instance_;\n    }\n```\n\nWhat happens for me is that `instance_ = new Client()` has been run and completed, but not `instance_.init()`. This happens when e.g. the user rotates the screen causing a new BackgroundThread to be started.\n\nI managed to hack around the delay by using `@UiThread(propagation = ENQUEUE)` and `getInstance_(Context)`, but I would rather not have to do all initialization of all beans on the MainThread (for performance reasons).\n","author":{"url":"https://github.com/tobias-","@type":"Person","name":"tobias-"},"datePublished":"2015-07-30T15:22:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":14},"url":"https://github.com/1507/androidannotations/issues/1507"}