Why is onCreate() in Activity protected?

Question

Why is the onCreate() in Activity protected?

or I should ask: why does it work?

Protected method can only be called in the inside of the class itself or it\'

Answer 1

onCreate is not public because you don't want a random class in a totally different package creating an activity.

If I design an Activity class in a com.abccompany.activity package, and one of my co-workers designs a JSON data parsing class in a com.abccompany.jsonparser package, I don't want him creating my activity and displaying his JSON data whenever he wants.

onCreate is not private because you do want to subclass an Activity and then use the super Activity onCreate method for the subclass.

Actually every Activity you design extends android.app.Activity, so if onCreate was private in that super class, then you wouldn't be able to call onCreate at all.

Answer 2

Why should you care wether the onCreate is protected? Is protected because logically it should not be accessed by other class different from Activities. How does Android launch the Activity? There are a lot of ways of doing that, specially if you're the one who designed the framework, the solution could be that is being invoked on the constructor (a possibility) o by other mechanisms like reflection with the appropriate privileges, etc.

The onClick is public because it could be set or handled by external classes that not necessary are your Activity. By this I mean that class A could be able to handle the onClick event of the Activity.

Answer 3

the onCeate() is protected so to avoid calling of it from the activity object.

MyActivity activity = new MyActivity();
activity.onCreate(args);  // which doesn't make sense because activity is not yet created

Since this method is only called when the activity gets created, calling it yourself will most probably give you a nullpointerException because the activity is not yet created.

Answer 4

It's useful to have public onClick methods because you can "force" certain buttons to be clicked programmatically. A common example of this is causing the same to code to execute when the user presses the enter key, or pressed the Submit button.

I don't think Android calls Activity.onCreate directly. Note that Activity inherits from Context (which does have a public constructor). It is my understanding that the constructor triggers some events to occur, and the onCreate/Pause/Resume/Destroy methods are called internally to the class at the appropriate time.

For example, when you create an activity, the view XML file has to be parsed and inflated. This happens automatically, so there's something happening behind the scenes that you don't directly control.