LifeCycle基本使用
1.1.声明一个监听的观察者，这里方法最多支持两个参数，且只有Any类型可以有两个，其他类型最多只能有一个参数，而且参数类型都固定，不可以定义其他类型
const val MTAG = "MLifeCycle"
class MLifeCycle : LifecycleObserver {
fun log(msg: String) {
Log.e(MTAG, msg)
}
@OnLifecycleEvent(Lifecycle.Event.ON_ANY)
fun onAny() {
log("onAny1 ")
}
@OnLifecycleEvent(Lifecycle.Event.ON_ANY)
fun onAny2(owener: LifecycleOwner, mEvent: Lifecycle.Event) {
log("onAny2 $mEvent " )
}
@OnLifecycleEvent(Lifecycle.Event.ON_CREATE)
fun onCreate(owener: LifecycleOwner) {
log("onCreate")
}
@OnLifecycleEvent(Lifecycle.Event.ON_START)
fun onStart() {
log("onStart")
}
@OnLifecycleEvent(Lifecycle.Event.ON_DESTROY)
fun onDestroy() {
log("onDestory")
}
@OnLifecycleEvent(Lifecycle.Event.ON_PAUSE)
fun onPause() {
log("onPause")
}
@OnLifecycleEvent(Lifecycle.Event.ON_RESUME)
fun onResume() {
log("onResume")
}1.2.在Activity中调用
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
......
lifecycle.addObserver(MLifeCycle())
}方法很简单，调用这句话就可以监听到页面的周期信息了
源码分析
先看下页面的入口处，这里有个核心代码
androidx.activity.ComponentActivity
@Override
protected void onCreate(@Nullable Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
mSavedStateRegistryController.performRestore(savedInstanceState);
ReportFragment.injectIfNeededIn(this);
if (mContentLayoutId != 0) {
setContentView(mContentLayoutId);
}
}在父类Activity中有个ReportFrgemtn的注入方法
public static void injectIfNeededIn(Activity activity) {
// ProcessLifecycleOwner should always correctly work and some activities may not extend
// FragmentActivity from support lib, so we use framework fragments for activities
android.app.FragmentManager manager = activity.getFragmentManager();
if (manager.findFragmentByTag(REPORT_FRAGMENT_TAG) == null) {
manager.beginTransaction().add(new ReportFragment(), REPORT_FRAGMENT_TAG).commit();
// Hopefully, we are the first to make a transaction.
manager.executePendingTransactions();
}
}这里实际上是给Activity中添加了一个ReportFragment ,而这个Fragment里面没有页面逻辑，只有一些生命周期监听的和分发的方法，这也是LifeCycle的核心，因为Fragent正常添加的生命周期和Activity基本上是同步的，通过这个Fragement的周期监听去推导Activity的生命周期，然后把状态发送给观察者
随便找一个生命周期
@Override
public void onResume() {
super.onResume();
dispatchResume(mProcessListener);
dispatch(Lifecycle.Event.ON_RESUME);
}
private void dispatch(Lifecycle.Event event) {
Activity activity = getActivity();
if (activity instanceof LifecycleRegistryOwner) {
((LifecycleRegistryOwner) activity).getLifecycle().handleLifecycleEvent(event);
return;
}
if (activity instanceof LifecycleOwner) {
Lifecycle lifecycle = ((LifecycleOwner) activity).getLifecycle();
if (lifecycle instanceof LifecycleRegistry) {
((LifecycleRegistry) lifecycle).handleLifecycleEvent(event);
}
}
}这里Fragment生命周期发生变化会去调用Activity中的getLifeCycle方法，获取到相应的LifeCycleOwner后再去调用handleLifecycleEvent把当前的LifeCycleEvent传递过去，后续就交给该对象去处理了
我们上面注册的时候也是用的这个方法 getLifeCyle().addObserver(...)添加的观察者，所以注册和处理全是在这个对象中
值得一提的是CompentActivity本身实现了LifecycleOwener方法
public class ComponentActivity extends androidx.core.app.ComponentActivity implements
LifecycleOwner,
ViewModelStoreOwner,
SavedStateRegistryOwner,
OnBackPressedDispatcherOwner { ... }而且LifecycleRegistryOwner已经被废弃，在新版api里已经没有调用，后续的我们就默认都是LifecycleOwner，本片主要讲Activity相关，所以也就算当前Activity本身（Fragment也实现了LifecycleOwner方法，周期方法也同样适用于Fragment）
@SuppressWarnings({"WeakerAccess", "unused"})
@Deprecated
public interface LifecycleRegistryOwner extends LifecycleOwner {
@NonNull
@Override
LifecycleRegistry getLifecycle();
}这个类目前已经被废弃
回到上面的getLifecycle()方法
androidx.activity.ComponentActivity
private final LifecycleRegistry mLifecycleRegistry = new LifecycleRegistry(this);
public Lifecycle getLifecycle() {
return mLifecycleRegistry;
}可以看出Activity中lifeCycle其实是这个LifecycleRegistry，而也是在这个类里面会处理注册和周期监管的所有逻辑
先看下构造方法
public LifecycleRegistry(@NonNull LifecycleOwner provider) {
mLifecycleOwner = new WeakReference<>(provider);
mState = INITIALIZED;
}这里用弱引用包装了这个provider，毕竟考虑到Activity引用泄露问题；然后会把当前的State状态设置成INITIALIZED
这里的State上篇也提到过，是当前页面状态的表示，有以下几个类型
public enum State {
DESTROYED,
INITIALIZED,
CREATED,
STARTED,
RESUMED;
public boolean isAtLeast(@NonNull State state) {
return compareTo(state) >= 0;
}
}这个顺序格式有严格要求，后续判断状态也用到了这些状态的顺序判断
然后上面提到了ReportFragment发送的LifecycleEvent则会和这个用一定的规则对应，先看下有哪些
public enum Event {
ON_CREATE,
ON_START,
ON_RESUME,
ON_PAUSE,
ON_STOP,
ON_DESTROY,
ON_ANY
}而后续会有一个方法进行对应，根据Event转换等价成对应的State
static State getStateAfter(Event event) {
switch (event) {
case ON_CREATE:
case ON_STOP:
return CREATED;
case ON_START:
case ON_PAUSE:
return STARTED;
case ON_RESUME:
return RESUMED;
case ON_DESTROY:
return DESTROYED;
case ON_ANY:
break;
}
throw new IllegalArgumentException("Unexpected event value " + event);
}可以看出转换并不是按周期一一对应的
Fragment的主要生命周期和Activity基本同步，而区别页面活动性的主要标记便是onResume这个生命周期；
当页面创建到显示的时候会经历 onCreate -> onStart -> onResume
当页面被其他页面覆盖会经历 onResume -> onPause -> onStop
当页面重新显示的时候会经历 onStop -> onPause -> onResume
以上列出了周期起始终止
而根据上面的转换State,三个过程分可以表示成
1. CREATED -> STARTED -> RESUME
2. RESUME -> STARTED -> CREATED
3. CREATED -> STARTED -> RESUME
这样可能还是感觉有点不直观，后续判断是根据枚举的ordinal值，比方说我把CREATED假定是1
1. 1 -> 2 -> 3 2. 3 ->2 -> 1 3. 1 -> 2 -> 3
也就是说从不活跃变成活跃是正序递增的state, 从活跃变成不活跃是递减，而上面的DESTROY状态是排在首位，不参与这个循环，一旦匹配就表示销毁了
然后我们看下注册的入口方法
@Override
public void addObserver(@NonNull LifecycleObserver observer) {
State initialState = mState == DESTROYED ? DESTROYED : INITIALIZED;
ObserverWithState statefulObserver = new ObserverWithState(observer, initialState);
ObserverWithState previous = mObserverMap.putIfAbsent(observer, statefulObserver);
if (previous != null) {
return;
}
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
// it is null we should be destroyed. Fallback quickly
return;
}
boolean isReentrance = mAddingObserverCounter != 0 || mHandlingEvent;
State targetState = calculateTargetState(observer);
mAddingObserverCounter++;
while ((statefulObserver.mState.compareTo(targetState) < 0
&& mObserverMap.contains(observer))) {
pushParentState(statefulObserver.mState);
statefulObserver.dispatchEvent(lifecycleOwner, upEvent(statefulObserver.mState));
popParentState();
// mState / subling may have been changed recalculate
targetState = calculateTargetState(observer);
}
if (!isReentrance) {
// we do sync only on the top level.
sync();
}
mAddingObserverCounter--;
}这里会先创建一个ObserverWithState对象，这里会存储我们注册的observer对象和状态信息，初始化时候initialState只有DESTROY和INITIALIZED两个状态
然后把这个对象添加到集合中，以observer作为key，如果key曾添加过，那么这里返回的previous就不为空，后续也就不执行
private State calculateTargetState(LifecycleObserver observer) {
Entry<LifecycleObserver, ObserverWithState> previous = mObserverMap.ceil(observer);
State siblingState = previous != null ? previous.getValue().mState : null;
State parentState = !mParentStates.isEmpty() ? mParentStates.get(mParentStates.size() - 1)
: null;
return min(min(mState, siblingState), parentState);
}这个方法会获取obsercerMap中的上一个注册的observer，并拿该状态和当前页面保存的状态进行对比，一般情况下，这两个状态都是相等的，而如果当期是新注册的observer，那么privious就为空，这个返回的就是当前页面的状态
最后会拿statefulObserver.mState这个状态和刚算出的页面状态进行比较，其实就是上面的两种销毁或初始化状态，而两个状态在声明的时候都比存活的生命周期靠前，所以条件正常是满足的，然后会调用dispacthEvent把事件发送出去，然后接着下一轮循环，一直到observer内的状态更新为和页面相同；就是说如果当前页面状态是Resume的，那么会把包括Resume在内的之前的状态全部分发一遍
比如上面的注册我用Handler延迟5000后再进行
Handler().postDelayed({
lifecycle.addObserver(MLifeCycle())
}, 5000
)打印的结果是
03-28 19:57:15.655 E/MLifeCycle: start delay handler
03-28 19:57:20.657 E/MLifeCycle: onCreate
03-28 19:57:20.657 E/MLifeCycle: onAny1
03-28 19:57:20.657 E/MLifeCycle: onAny2 ON_CREATE
03-28 19:57:20.657 E/MLifeCycle: onStart
03-28 19:57:20.657 E/MLifeCycle: onAny1
03-28 19:57:20.657 E/MLifeCycle: onAny2 ON_START
03-28 19:57:20.657 E/MLifeCycle: onResume
03-28 19:57:20.657 E/MLifeCycle: onAny1
03-28 19:57:20.657 E/MLifeCycle: onAny2 ON_RESUME 也就验证了我们的想法
看下upEvent方法
private static Event upEvent(State state) {
switch (state) {
case INITIALIZED:
case DESTROYED:
return ON_CREATE;
case CREATED:
return ON_START;
case STARTED:
return ON_RESUME;
case RESUMED:
throw new IllegalArgumentException();
}
throw new IllegalArgumentException("Unexpected state value " + state);
}可以看出，这里计算的是下一个生命周期，上面的首次往后推算的就是ON_CREATE这个，同样也会有往前推算的方法
private static Event downEvent(State state) {
switch (state) {
case INITIALIZED:
throw new IllegalArgumentException();
case CREATED:
return ON_DESTROY;
case STARTED:
return ON_STOP;
case RESUMED:
return ON_PAUSE;
case DESTROYED:
throw new IllegalArgumentException();
}
throw new IllegalArgumentException("Unexpected state value " + state);
}回到上面的对象创建，上面创建了一个ObsrverWithState对象
static class ObserverWithState {
State mState;
LifecycleEventObserver mLifecycleObserver;
ObserverWithState(LifecycleObserver observer, State initialState) {
mLifecycleObserver = Lifecycling.lifecycleEventObserver(observer);
mState = initialState;
}
void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = getStateAfter(event);
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}
}这里会把把observer包装成一个LifecyclleEventObserver，发送事件的时候会调用该对象的onStateChanged方法，并把自身的状态更改为新状态，具体分发先放着，后面讲
上面提到，ReportFragment状态变更会调用相应的LifeCycle的handleLifecycleEvent方法传递
public void handleLifecycleEvent(@NonNull Lifecycle.Event event) {
State next = getStateAfter(event);
moveToState(next);
}先把相应的Event对应成上面的枚举状态类型，然后调用moveToState方法
private void moveToState(State next) {
if (mState == next) {
return;
}
mState = next;
if (mHandlingEvent || mAddingObserverCounter != 0) {
mNewEventOccurred = true;
// we will figure out what to do on upper level.
return;
}
mHandlingEvent = true;
sync();
mHandlingEvent = false;
}这里会有状态判断，状态不同的才能执行下一步，并把状态更新成最新状态
private void sync() {
LifecycleOwner lifecycleOwner = mLifecycleOwner.get();
if (lifecycleOwner == null) {
throw new IllegalStateException("LifecycleOwner of this LifecycleRegistry is already"
+ "garbage collected. It is too late to change lifecycle state.");
}
while (!isSynced()) {
mNewEventOccurred = false;
// no need to check eldest for nullability, because isSynced does it for us.
if (mState.compareTo(mObserverMap.eldest().getValue().mState) < 0) {
backwardPass(lifecycleOwner);
}
Entry<LifecycleObserver, ObserverWithState> newest = mObserverMap.newest();
if (!mNewEventOccurred && newest != null
&& mState.compareTo(newest.getValue().mState) > 0) {
forwardPass(lifecycleOwner);
}
}
mNewEventOccurred = false;
}这里会有两种状态判断
1.取mObserverMap中的第一个元素的状态，如果当前页面的状态小于该元素的状态调用backwardPass方法
2.去mObserverMap中最后一个元素的状态，如果当前页面的状态大于该元素的状态调用forwardPass方法
这里的计算还是依据上面提到的枚举判断
这两个方法也是有些许差异
private void backwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> descendingIterator =
mObserverMap.descendingIterator();
while (descendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = descendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) > 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
Event event = downEvent(observer.mState);
pushParentState(getStateAfter(event));
observer.dispatchEvent(lifecycleOwner, event);
popParentState();
}
}
}这里有个倒叙遍历迭代器，我们再分析一下上面的状态变化；当页面状态小于该元素状态，对应于上面的流程2
RESUME -> STARTED -> CREATED
根据上面的算法，这里相当于是从resume->onpause->onstop，也就是说页面变更成不活跃的状态
然后会倒叙遍历观察者obvserver，然后通过downEvent推算下一个生命周期，依次发送消息
比如我顺序注册了observer1, observer2,observer3 这三个观察对象，当页面变更成不活跃的状态时，会按照顺序先通知observer3的周期Event的变更 ON_PAUSE->ON_STOP，然后通知observer2的，最后通知observer1的
相反forwardPass方法则是正序通知
private void forwardPass(LifecycleOwner lifecycleOwner) {
Iterator<Entry<LifecycleObserver, ObserverWithState>> ascendingIterator =
mObserverMap.iteratorWithAdditions();
while (ascendingIterator.hasNext() && !mNewEventOccurred) {
Entry<LifecycleObserver, ObserverWithState> entry = ascendingIterator.next();
ObserverWithState observer = entry.getValue();
while ((observer.mState.compareTo(mState) < 0 && !mNewEventOccurred
&& mObserverMap.contains(entry.getKey()))) {
pushParentState(observer.mState);
observer.dispatchEvent(lifecycleOwner, upEvent(observer.mState));
popParentState();
}
}
}当页面状态小于该元素状态，对应于上面的流程1或3
CREATED -> STARTED -> RESUME
根据上面的算法，这里相当于是从onCreate -> onStart -> onResume 或者 onstop->onpause->resume
也就是说页面变更成活跃的状态
这里是正序迭代器，通过upEvent向前推算周期，上面的通知顺序则变成observer1 -> observer2 -> observer3
比如上面的例子，我简化部分周期，并注册三个观察者
当页面创建到展示时
E/MLifeCycle 1: onCreate
E/MLifeCycle 2: onCreate
E/MLifeCycle 3: onCreate
E/MLifeCycle 1: onStart
E/MLifeCycle 2: onStart
E/MLifeCycle 3: onStart
E/MLifeCycle 1: onResume
E/MLifeCycle 2: onResume
E/MLifeCycle 3: onResume当返回桌面时候
E/MLifeCycle 3: onPause
E/MLifeCycle 2: onPause
E/MLifeCycle 1: onPause
E/MLifeCycle 3: onStop
E/MLifeCycle 2: onStop
E/MLifeCycle 1: onStop再重新打开页面时候
E/MLifeCycle 1: onStart
E/MLifeCycle 2: onStart
E/MLifeCycle 3: onStart
E/MLifeCycle 1: onResume
E/MLifeCycle 2: onResume
E/MLifeCycle 3: onResume这和我们上面的推断是符合的
接下来回到上面提到的分发的方法，首先会创建一个LifecycleEventObserver，然后调用这个对象的onStateChanged方法
static class ObserverWithState {
State mState;
LifecycleEventObserver mLifecycleObserver;
ObserverWithState(LifecycleObserver observer, State initialState) {
mLifecycleObserver = Lifecycling.lifecycleEventObserver(observer);
mState = initialState;
}
void dispatchEvent(LifecycleOwner owner, Event event) {
State newState = getStateAfter(event);
mState = min(mState, newState);
mLifecycleObserver.onStateChanged(owner, event);
mState = newState;
}
}这里需要关注一下这个创建方法
static LifecycleEventObserver lifecycleEventObserver(Object object) {
boolean isLifecycleEventObserver = object instanceof LifecycleEventObserver;
boolean isFullLifecycleObserver = object instanceof FullLifecycleObserver;
if (isLifecycleEventObserver && isFullLifecycleObserver) {
return new FullLifecycleObserverAdapter((FullLifecycleObserver) object,
(LifecycleEventObserver) object);
}
if (isFullLifecycleObserver) {
return new FullLifecycleObserverAdapter((FullLifecycleObserver) object, null);
}
if (isLifecycleEventObserver) {
return (LifecycleEventObserver) object;
}
final Class<?> klass = object.getClass();
int type = getObserverConstructorType(klass);
if (type == GENERATED_CALLBACK) {
List<Constructor<? extends GeneratedAdapter>> constructors =
sClassToAdapters.get(klass);
if (constructors.size() == 1) {
GeneratedAdapter generatedAdapter = createGeneratedAdapter(
constructors.get(0), object);
return new SingleGeneratedAdapterObserver(generatedAdapter);
}
GeneratedAdapter[] adapters = new GeneratedAdapter[constructors.size()];
for (int i = 0; i < constructors.size(); i++) {
adapters[i] = createGeneratedAdapter(constructors.get(i), object);
}
return new CompositeGeneratedAdaptersObserver(adapters);
}
return new ReflectiveGenericLifecycleObserver(object);
}这里有两种主要类型区分，一种是依赖GenerateAdapter自动生成，一种是通过反射
自动生成方法需要配置依赖编译器，kotlin的依赖是这个 ; java的把kapt替换成annotationProcessor
kapt "androidx.lifecycle:lifecycle-compiler:2.0.0"
然后上面的MLifeCycle编译后生成的文件是
public class MLifeCycle_LifecycleAdapter implements GeneratedAdapter {
final MLifeCycle mReceiver;
MLifeCycle_LifecycleAdapter(MLifeCycle receiver) {
this.mReceiver = receiver;
}
@Override
public void callMethods(LifecycleOwner owner, Lifecycle.Event event, boolean onAny,
MethodCallsLogger logger) {
boolean hasLogger = logger != null;
if (onAny) {
if (!hasLogger || logger.approveCall("onAny", 1)) {
mReceiver.onAny();
}
if (!hasLogger || logger.approveCall("onAny2", 4)) {
mReceiver.onAny2(owner,event);
}
return;
}
if (event == Lifecycle.Event.ON_CREATE) {
if (!hasLogger || logger.approveCall("onCreate", 2)) {
mReceiver.onCreate(owner);
}
return;
}
if (event == Lifecycle.Event.ON_START) {
if (!hasLogger || logger.approveCall("onStart", 1)) {
mReceiver.onStart();
}
return;
}
if (event == Lifecycle.Event.ON_DESTROY) {
if (!hasLogger || logger.approveCall("onDestroy", 1)) {
mReceiver.onDestroy();
}
return;
}
if (event == Lifecycle.Event.ON_PAUSE) {
if (!hasLogger || logger.approveCall("onPause", 1)) {
mReceiver.onPause();
}
return;
}
if (event == Lifecycle.Event.ON_RESUME) {
if (!hasLogger || logger.approveCall("onResume", 1)) {
mReceiver.onResume();
}
return;
}
}
}里面进行Lifecycle.Event判断，直接调用我们注册的observer的相应Event对应的方法，这个很简单；我们再看下反射类型的代码
class ReflectiveGenericLifecycleObserver implements LifecycleEventObserver {
private final Object mWrapped;
private final CallbackInfo mInfo;
ReflectiveGenericLifecycleObserver(Object wrapped) {
mWrapped = wrapped;
mInfo = ClassesInfoCache.sInstance.getInfo(mWrapped.getClass());
}
@Override
public void onStateChanged(LifecycleOwner source, Event event) {
mInfo.invokeCallbacks(source, event, mWrapped);
}
}这里会有一个存储注册信息的类，然后这里的onStateChanged方法会通过反射去回调对应的方法，看下这里的通知的方法
static class CallbackInfo {
final Map<Lifecycle.Event, List<MethodReference>> mEventToHandlers;
final Map<MethodReference, Lifecycle.Event> mHandlerToEvent;
CallbackInfo(Map<MethodReference, Lifecycle.Event> handlerToEvent) {
mHandlerToEvent = handlerToEvent;
mEventToHandlers = new HashMap<>();
for (Map.Entry<MethodReference, Lifecycle.Event> entry : handlerToEvent.entrySet()) {
Lifecycle.Event event = entry.getValue();
List<MethodReference> methodReferences = mEventToHandlers.get(event);
if (methodReferences == null) {
methodReferences = new ArrayList<>();
mEventToHandlers.put(event, methodReferences);
}
methodReferences.add(entry.getKey());
}
}
@SuppressWarnings("ConstantConditions")
void invokeCallbacks(LifecycleOwner source, Lifecycle.Event event, Object target) {
invokeMethodsForEvent(mEventToHandlers.get(event), source, event, target);
invokeMethodsForEvent(mEventToHandlers.get(Lifecycle.Event.ON_ANY), source, event,
target);
}
private static void invokeMethodsForEvent(List<MethodReference> handlers,
LifecycleOwner source, Lifecycle.Event event, Object mWrapped) {
if (handlers != null) {
for (int i = handlers.size() - 1; i >= 0; i--) {
handlers.get(i).invokeCallback(source, event, mWrapped);
}
}
}
}这里存了两个Map
一个是Lifecycle.Event 对应的所有方法信息，一对多，一个Event能同时注册多个方法
一个是方法对应的Event类型，一对一，一个方法只能对应一个Event
每次事件产生都会同时发送两次事件，一个是当前发送的Event，另一个是ON_ANY类型，这个类型是每次都会发送
invokeCallbacks方法会遍历当前Event对应的所有方法信息，全部调用一遍
mEventToHandlers是通过mHandlerToEvent遍历生成的
static class MethodReference {
final int mCallType;
final Method mMethod;
MethodReference(int callType, Method method) {
mCallType = callType;
mMethod = method;
mMethod.setAccessible(true);
}
void invokeCallback(LifecycleOwner source, Lifecycle.Event event, Object target) {
//noinspection TryWithIdenticalCatches
try {
switch (mCallType) {
case CALL_TYPE_NO_ARG:
mMethod.invoke(target);
break;
case CALL_TYPE_PROVIDER:
mMethod.invoke(target, source);
break;
case CALL_TYPE_PROVIDER_WITH_EVENT:
mMethod.invoke(target, source, event);
break;
}
} catch (InvocationTargetException e) {
throw new RuntimeException("Failed to call observer method", e.getCause());
} catch (IllegalAccessException e) {
throw new RuntimeException(e);
}
}
}MethodRefence方法则会通过反射去调用存储的方法信息，可以看出没最多有两个参数类型，同时两个类型都是指定类型，顺序也是固定的，分别是LifecycleOwner和Lifecycle.Event
回到上面的创建方法
private final Map<Class, CallbackInfo> mCallbackMap = new HashMap<>();
CallbackInfo getInfo(Class klass) {
CallbackInfo existing = mCallbackMap.get(klass);
if (existing != null) {
return existing;
}
existing = createInfo(klass, null);
return existing;
}这里会用一个Map缓存当前类的信息
private CallbackInfo createInfo(Class klass, @Nullable Method[] declaredMethods) {
Class superclass = klass.getSuperclass();
Map<MethodReference, Lifecycle.Event> handlerToEvent = new HashMap<>();
if (superclass != null) {
CallbackInfo superInfo = getInfo(superclass);
if (superInfo != null) {
handlerToEvent.putAll(superInfo.mHandlerToEvent);
}
}
Class[] interfaces = klass.getInterfaces();
for (Class intrfc : interfaces) {
for (Map.Entry<MethodReference, Lifecycle.Event> entry : getInfo(
intrfc).mHandlerToEvent.entrySet()) {
verifyAndPutHandler(handlerToEvent, entry.getKey(), entry.getValue(), klass);
}
}
Method[] methods = declaredMethods != null ? declaredMethods : getDeclaredMethods(klass);
boolean hasLifecycleMethods = false;
for (Method method : methods) {
OnLifecycleEvent annotation = method.getAnnotation(OnLifecycleEvent.class);
if (annotation == null) {
continue;
}
hasLifecycleMethods = true;
Class<?>[] params = method.getParameterTypes();
int callType = CALL_TYPE_NO_ARG;
if (params.length > 0) {
callType = CALL_TYPE_PROVIDER;
if (!params[0].isAssignableFrom(LifecycleOwner.class)) {
throw new IllegalArgumentException(
"invalid parameter type. Must be one and instanceof LifecycleOwner");
}
}
Lifecycle.Event event = annotation.value();
if (params.length > 1) {
callType = CALL_TYPE_PROVIDER_WITH_EVENT;
if (!params[1].isAssignableFrom(Lifecycle.Event.class)) {
throw new IllegalArgumentException(
"invalid parameter type. second arg must be an event");
}
if (event != Lifecycle.Event.ON_ANY) {
throw new IllegalArgumentException(
"Second arg is supported only for ON_ANY value");
}
}
if (params.length > 2) {
throw new IllegalArgumentException("cannot have more than 2 params");
}
MethodReference methodReference = new MethodReference(callType, method);
verifyAndPutHandler(handlerToEvent, methodReference, event, klass);
}
CallbackInfo info = new CallbackInfo(handlerToEvent);
mCallbackMap.put(klass, info);
mHasLifecycleMethods.put(klass, hasLifecycleMethods);
return info;
}这个创建的方法比较好理解，会遍历当前类的所有方法，获取有OnLifecycleEvent注解的方法，然后获取对应的value值，判断有无形参，如果有判断形参类型是否匹配，不匹配直接抛出异常；最后把方法和Event一一对应保存在CallBackInfo中的Map里，方便后续反射调用
private void verifyAndPutHandler(Map<MethodReference, Lifecycle.Event> handlers,
MethodReference newHandler, Lifecycle.Event newEvent, Class klass) {
Lifecycle.Event event = handlers.get(newHandler);
if (event != null && newEvent != event) {
Method method = newHandler.mMethod;
throw new IllegalArgumentException(
"Method " + method.getName() + " in " + klass.getName()
+ " already declared with different @OnLifecycleEvent value: previous"
+ " value " + event + ", new value " + newEvent);
}
if (event == null) {
handlers.put(newHandler, newEvent);
}
}这个方法会有缓存判断，同一个方法只能对应一个Event；这里整个流程就分析完毕了
总结
1.Lifecycle通过向Activity里添加一个ReportFragment，并监听这个Fragment的生命周期变化，并把变更的状态通过LifeEvent传递给注册的Observer
2.自定义LifecycleObserver方法参数有限制，普通类型最多支持一个参数，Any类型最多支持两个参数；且参数类型和顺序也有限制，必须为LifecycleOwner和Lifecycle.Event
3.声明的Any类型方法每次事件发送都会调用，其他类型的只有当该类型事件触发才会调用；也可以只定义一个Any类型的方法，用其中的第二个参数类型Event类型进行判断处理相应的逻辑
4.当Oserver对象被注册时，会依次触发对应的周期方法，并更新相应的状态信息，直到与当期页面状态相同；也就是说，如果页面已经是Resume状态，那么这个状态前面的周期也会依次回调，直到调用到声明的Resume方法如果有的话，确保周期的完整性；类似于粘性注册
5.Fragment的LifecycleEvent会按照一定规则对应成State的状态信息，主要是onPause和onStop会有所不同；onPause会对应成State的START状态，onStop会对应成CREATED状态；这样的好处是，页面变更成活跃状态时（包含第一次创建），状态的枚举ordinal值是增大的，而页面变更为不活跃状态时，状态的ordinal值是减小的，方便后面推断和计算
6.根据页面状态变更流程的不同，注册的回调顺序也有差异，这里主要是根
6.1 页面从不活跃变更成活跃状态时候，会按照注册的顺序依次通知周期变更
6.2页面从活跃变更成不活跃状态的时候，会按照注册的顺序逆序通知周期变更
7.当生命周期变更时，会直接拿到页面的LifeCycle对象，并通过调用handleLifecycleEvent方法传递当期的周期Event事件，而这最终会通过适配器或者反射方式去调用我们注册的LifecycleObserver的相应标记的Event方法；这里分为两种
7.1 适配器模式，这个是编译器自动生成的，需要引入相应编译依赖，这个会把注册的LifecycleObserver传入，并在方法中进行Event判断，选择调用标记过的相应的Event方法
7.2 当不引入编译依赖，运行时会通过反射去实现同样的功能；
运行时会先遍历当前注册的LifecycleObserver中所有的方法，获取有Event标记的，然后把该方法和Event进行对应并缓存到map集合中，形成Map<方法信息，Event>的结构，并根据这个结构额外创建一个新的Map缓存，结构是Map<Event,List<方法信息> ;
其中第一个Map是一对一的关系，一个方法只能对应一个周期Event配置，第二个是一对多的关系，一个Event可以对应多个声明的方法；
当外部调用变更通知方法时，会把当期要变更的Event传递进来，然后通过上面定义的Map查询出所对应的所有方法，如果有声明，那么就依次反射调用这些方法，这样实际上也是去调用我们注册的Observer内的方法
补上大致的流程图
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
