Android源代碼之DeskClock (三) Proxy/Delegate Application 框架應用
阿新 • • 發佈：2017-07-06
源代碼 sna 還記得 java cep info avi 配置文件 cit
2.使用Proxy/Delegate框架之後 使用Proxy/Delegate框架,須要又一次構建出來一個新的ProxyApplication,用來做代理Application,原先的MyApplication的作用為DelegateApplication 所以Manifest的配置須要更改,app的主入口更改為MyProxyApplication,把DelegateApplication的信息以meta-data子元素的形式存儲(當然也能夠用其它的方式)
入口的順序沒問題了之後,就能夠在initProxyApplication方法中替換當前的ClassLoader到父類的ClassLoader,而且在MyProxyApplication的onCreate中將應用層全部的Application的引用全部從ProxyApplication替換成MyApplication(當前在DeskClock程序中沒有替換ClassLoader的需求,僅僅須要替換全部的Application的引用就能達到代理的效果,所以在initProxyApplication方法處就寫了一個空方法帶過). 先從AndroidManifest配置文件裏的metadata拿到DelegateApplication的屬性
可是這樣還沒有全然結束,還記得開頭說的ContentProvider嗎?他的構造是在Application的onCreate之前的,那麽ContentProvider部分有沒有須要替換的Context引用呢？從framework/base/core/java/android/app下能夠找到ActivityThread.java從當中裝載ContentProvider的部分能夠看到,假設當前Context的包名和ProviderInfo的包名一樣的話,ContentProvider就會引用當前的MyProxyApplication的Context.因為當前的MyProxyApplication僅僅是做代理啟動用的,所以在MyProxyApplication處復寫getPackageName而且返回空就能夠避免ContentProvider復用當前Context了.
一.概述
當項目有加殼子,插件化或熱修復等需求的時候,能夠使用Proxy/Delegate Application框架的方式,在正常的模式中,一個程序一般僅僅有一個Application入口,而Proxy/Delegate模式中須要有兩個Application,原程序的Application改為Delegate Application,再新加一個Proxy Application,由Proxy Application 提供一系列的個性化定制,再將所有的context和context相關的引用所有轉化為Delegate Application的實例,讓外界包含Delegate Application自身都以為該App的Application入口就是Delegate Application.二.實例
1.Proxy/Delegate 之前 這裏就在Android 4.4原生的DeskClock程序上應用Proxy/Delegate框架為演示樣例 原生的DeskClock程序沒有自己定義Application,這裏先定義一個,並print該程序眼下ApplicationContext的名字(在DeskClock中使用的Log是自己定義的)/**
* Created by jesse on 15-7-17.
*/
public class MyApplication extends Application{
private final String TAG = MyApplication.class.getSimpleName();
@Override
public void onCreate() {
super.onCreate();
Log.i(TAG + ", onCreate " + this.getApplicationContext().getClass().getSimpleName());
}
} <application android:name="cn.jesse.MyApplication"
android:label="@string/app_label"
android:icon="@mipmap/ic_launcher_alarmclock"
android:requiredForAllUsers="true"
android:supportsRtl="true">2.使用Proxy/Delegate框架之後 使用Proxy/Delegate框架,須要又一次構建出來一個新的ProxyApplication,用來做代理Application,原先的MyApplication的作用為DelegateApplication 所以Manifest的配置須要更改,app的主入口更改為MyProxyApplication,把DelegateApplication的信息以meta-data子元素的形式存儲(當然也能夠用其它的方式)
<application android:name="cn.jesse.MyProxyApplication"
android:label="@string/app_label"
android:icon="@mipmap/ic_launcher_alarmclock"
android:requiredForAllUsers="true"
android:supportsRtl="true">
<meta-data
android:name="DELEGATE_APPLICATION_CLASS_NAME"
android:value="cn.jesse.MyApplication" >
</meta-data>
</application>
定義一個抽象類,提供一個用於替換當前ProxyApplication 的ClassLoader成父類的ClassLoader的抽象方法(或者一些其它的個性化定制)
* Created by jesse on 15-7-17.
*/
public abstract class ProxyApplication extends Application{
protected abstract void initProxyApplication();
} 當我們要替換當前ProxyApplication的ClassLoader為父類的ClassLoader,所以這個替換的動作要足夠得早(要保證在app Context最早被構建的入口處替換ClassLoader),要不然就會出現替換不幹凈的情況,就會有程序中大部分使用的DelegateApplication的ClassLoader,而一小部分是使用的ProxyApplication的ClassLoader,這樣可能會出現一些意想不到的bug.
通常來說在Application的OnCreate中來做替換就足夠了,可是當app有註冊ContentProvider的時候ContentProvider：OnCreate的調用是在Application:OnCreate之前的,所以我們必須保證替換ClassLoader的動作要在ContentProvider之前.
通過查看源代碼能夠看到Application是繼承自ContextWrapper,而在ContextWrapper中系統在構建完畢完好的Context之後第一次回調是通過attachBaseContext方法,既然這樣就通過在ProxyApplication中復寫該方法來獲取剛出爐熱噴噴的Context來轉換ClassLoader.
/**
* Set the base context for this ContextWrapper. All calls will then be
* delegated to the base context. Throws
* IllegalStateException if a base context has already been set.
*
* @param base The new base context for this wrapper.
*/
protected void attachBaseContext(Context base) {
if (mBase != null) {
throw new IllegalStateException("Base context already set");
}
mBase = base;
} 轉換ClassLoader的入口也確定之後就能夠自己定義一個MyProxyApplication,繼承自ProxyApplication而且復寫attachBaseContext方法,print相關信息
/**
* Created by jesse on 15-7-17.
*/
public class MyProxyApplication extends ProxyApplication {
private final String TAG = MyProxyApplication.class.getSimpleName();
private Context mContext;
@Override
protected void attachBaseContext(Context base) {
super.attachBaseContext(base);
Log.i(TAG + ", attachBaseContext");
mContext = base;
this.initProxyApplication();
}
@Override
public void onCreate() {
super.onCreate();
Log.i(TAG + ", onCreate" + this.getApplicationContext().getClass().getSimpleName());
BootLoader.boot(mContext);
}
@Override
protected void initProxyApplication() {
Log.i(TAG + ", initProxyApplication");
BootLoader.resetClassLoader(mContext);
}
} Log執行的順序,先進入attachBaseContext->initProxyApplication->onCreate->DeskClock:onCreate (這裏DeskClock的onCreate獲取到的ApplicationContext的名字是(MyProxyApplication)
入口的順序沒問題了之後,就能夠在initProxyApplication方法中替換當前的ClassLoader到父類的ClassLoader,而且在MyProxyApplication的onCreate中將應用層全部的Application的引用全部從ProxyApplication替換成MyApplication(當前在DeskClock程序中沒有替換ClassLoader的需求,僅僅須要替換全部的Application的引用就能達到代理的效果,所以在initProxyApplication方法處就寫了一個空方法帶過). 先從AndroidManifest配置文件裏的metadata拿到DelegateApplication的屬性
String className = CLASS_NAME;
ApplicationInfo appInfo = getPackageManager().getApplicationInfo(super.getPackageName(), PackageManager.GET_META_DATA);
Bundle bundle = appInfo.metaData;
if (bundle != null && bundle.containsKey(KEY)) {
className = bundle.getString(KEY);
if (className.startsWith("."))
className = super.getPackageName() + className;
} 依據className反射得到MyApplication,創建MyApplication實例而且取得MyProxyApplication的實例 Class delegateClass = Class.forName(className, true, getClassLoader());
Application delegate = (Application) delegateClass.newInstance();
Application proxyApplication = (Application)getApplicationContext(); 使用反射更換MyProxyApplication context成員中的mOuterContext屬性
Class contextImplClass = Class.forName("android.app.ContextImpl");
Field mOuterContext = contextImplClass.getDeclaredField("mOuterContext");
mOuterContext.setAccessible(true);
mOuterContext.set(mContext, delegate);
獲取MyProxyApplication Context的PackageInfo對象,替換掉當中的mApplication屬性
Field mPackageInfoField = contextImplClass.getDeclaredField("mPackageInfo");
mPackageInfoField.setAccessible(true);
Object mPackageInfo = mPackageInfoField.get(mContext);
Class loadedApkClass = Class.forName("android.app.LoadedApk");
Field mApplication = loadedApkClass.getDeclaredField("mApplication");
mApplication.setAccessible(true);
mApplication.set(mPackageInfo, delegate);
再依據之前反射得到的packageInfo對象獲取到mActivityThread屬性,替換掉當中的mInitialApplication屬性
Class activityThreadClass = Class.forName("android.app.ActivityThread");
Field mAcitivityThreadField = loadedApkClass.getDeclaredField("mActivityThread");
mAcitivityThreadField.setAccessible(true);
Object mActivityThread = mAcitivityThreadField.get(mPackageInfo);
Field mInitialApplicationField = activityThreadClass.getDeclaredField("mInitialApplication");
mInitialApplicationField.setAccessible(true);
mInitialApplicationField.set(mActivityThread, delegate);
拿著之前的mActivityThread對象獲取到mAllApplications屬性,註意該屬性是一個list。這裏就移除MyProxyApplication加入DelegateApplication,至此應用層MyProxyApplication的Context的引用所有都替換成了MyApplication的引用.
Field mAllApplicationsField = activityThreadClass.getDeclaredField("mAllApplications");
mAllApplicationsField.setAccessible(true);
ArrayList<Application> al = (ArrayList<Application>)mAllApplicationsField.get(mActivityThread);
al.add(delegate);
al.remove(proxyApplication);
給MyApplication通過反射和attach內部方法設置baseContext,並調用MyApplication的onCreate方法完畢DelegateApplication的初始化.
Method attach = Application.class.getDeclaredMethod("attach", Context.class);
attach.setAccessible(true);
attach.invoke(delegate, mContext);
delegate.onCreate(); 完畢這些步驟之後再又一次執行查看Log,觀察DeskClock處獲取的ApplicationContext的名字已經變成MyApplication.
可是這樣還沒有全然結束,還記得開頭說的ContentProvider嗎?他的構造是在Application的onCreate之前的,那麽ContentProvider部分有沒有須要替換的Context引用呢？從framework/base/core/java/android/app下能夠找到ActivityThread.java從當中裝載ContentProvider的部分能夠看到,假設當前Context的包名和ProviderInfo的包名一樣的話,ContentProvider就會引用當前的MyProxyApplication的Context.因為當前的MyProxyApplication僅僅是做代理啟動用的,所以在MyProxyApplication處復寫getPackageName而且返回空就能夠避免ContentProvider復用當前Context了.
private IActivityManager.ContentProviderHolder installProvider(Context context,
IActivityManager.ContentProviderHolder holder, ProviderInfo info,
boolean noisy, boolean noReleaseNeeded, boolean stable) {
ContentProvider localProvider = null;
IContentProvider provider;
if (holder == null || holder.provider == null) {
if (DEBUG_PROVIDER || noisy) {
Slog.d(TAG, "Loading provider " + info.authority + ": "
+ info.name);
}
Context c = null;
ApplicationInfo ai = info.applicationInfo;
if (context.getPackageName().equals(ai.packageName)) {
c = context;
} else if (mInitialApplication != null &&
mInitialApplication.getPackageName().equals(ai.packageName)) {
c = mInitialApplication;
} else {
try {
c = context.createPackageContext(ai.packageName,
Context.CONTEXT_INCLUDE_CODE);
} catch (PackageManager.NameNotFoundException e) {
// Ignore
}
}
三.總結
這篇僅僅是先簡單的走了下Proxy/Delegate框架的流程,這個框架事實上是有非常多使用場景的,比如多dex動態載入,插件化,線上程序熱修復bug等能夠靈活使用出非常多有趣的技術,有時間的話還會再發一篇以Proxy/Delegate實現的線上程序熱修復bug的博客.轉載請註明出處:http://blog.csdn.net/l2show/article/details/46914881
Android源代碼之DeskClock (三) Proxy/Delegate Application 框架應用