RxJava2 封装主要变化
- Transformer的变化:RxJava1.X为rx.Observable.Transformer接口, 继承自Func1<Observable<T>, Observable<R>>, RxJava2.X为io.reactivex.ObservableTransformer<pstream, Downstream>,是一个独立的接口。
- Flowable则是FlowableTransformer，如果你使用Flowable，以下ObservableTransformer替换FlowableTransformer即可。
封装方案
1、封装 Rx 线程相关
RxSchedulersHelper：1
2
3
4
5
6
7
8
9
10/**
* Created by weiss on 17/1/16.
*/
public class RxSchedulers {
public static <T> ObservableTransformer<T, T> io_main() {
return upstream ->
upstream.subscribeOn(Schedulers.io())
.observeOn(AndroidSchedulers.mainThread());
}
}
封装后：1
2
3Api.getInstance().movieService
.getGankData("Android",1)
.compose(RxSchedulers.io_main());
2、封装 处理服务器返回数据，管理 RxJava生命周期
HttpResult：
1 | /** |
BaseRxActivity：1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
/**
* 管理RxJava生命周期，避免内存泄漏
* RxJava处理服务器返回
*
* Created by Weiss on 2016/12/23.
*/
public abstract class BaseRxActivity extends BaseActivity {
private CompositeDisposable disposables2Stop;// 管理Stop取消订阅者者
private CompositeDisposable disposables2Destroy;// 管理Destroy取消订阅者者
protected abstract int getLayoutId();
protected abstract void initView();
/**
* Rx优雅处理服务器返回
*
* @param <T>
* @return
*/
public <T> ObservableTransformer<HttpResult<T>, T> handleResult() {
return upstream ->{
return upstream.flatMap(result -> {
if (result.isSuccess()) {
return createData(result.data);
} else if (result.isTokenInvalid()) {
//处理token失效，tokenInvalid方法在BaseActivity 实现
tokenInvalid();
} else {
return Observable.error(new Exception(result.msg));
}
return Observable.empty();
}
);
};
}
private <T> Observable<T> createData(final T t) {
return Observable.create(subscriber -> {
try {
subscriber.onNext(t);
subscriber.onComplete();
} catch (Exception e) {
subscriber.onError(e);
}
});
}
public boolean addRxStop(Disposable disposable) {
if (disposables2Stop == null) {
throw new IllegalStateException(
"addUtilStop should be called between onStart and onStop");
}
disposables2Stop.add(disposable);
return true;
}
public boolean addRxDestroy(Disposable disposable) {
if (disposables2Destroy == null) {
throw new IllegalStateException(
"addUtilDestroy should be called between onCreate and onDestroy");
}
disposables2Destroy.add(disposable);
return true;
}
public void remove(Disposable disposable) {
if (disposables2Stop == null && disposables2Destroy == null) {
throw new IllegalStateException("remove should not be called after onDestroy");
}
if (disposables2Stop != null) {
disposables2Stop.remove(disposable);
}
if (disposables2Destroy != null) {
disposables2Destroy.remove(disposable);
}
}
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
if (disposables2Destroy != null) {
throw new IllegalStateException("onCreate called multiple times");
}
disposables2Destroy = new CompositeDisposable();
}
public void onStart() {
super.onStart();
if (disposables2Stop != null) {
throw new IllegalStateException("onStart called multiple times");
}
disposables2Stop = new CompositeDisposable();
}
public void onStop() {
super.onStop();
if (disposables2Stop == null) {
throw new IllegalStateException("onStop called multiple times or onStart not called");
}
disposables2Stop.dispose();
disposables2Stop = null;
}
public void onDestroy() {
super.onDestroy();
if (disposables2Destroy == null) {
throw new IllegalStateException(
"onDestroy called multiple times or onCreate not called");
}
disposables2Destroy.dispose();
disposables2Destroy = null;
}
}
封装后 (BaseRxActivity的子类使用)：1
2
3
4
5
6addRxDestroy(Api.getInstance().movieService
.getGankData("Android",1)
.compose(RxSchedulers.io_main())
.compose(handleResult())
.省略
);
handleResult为什么不新建一个类处理呢？因为很多异常处理需要context对象，或者和BaseActivity有千丝万缕的联系，BaseRxActivity继承BaseActivity可以很简洁优雅处理各种异常。比如token失效，是需要跳转到登录页面的。在新建一个类中，不能持有context对象，只能使用Application的Context，同时方便与Activity通信交互满足各种需求。BaseRxActivity还可以管理RxJava生命周期。
3、异常处理
1 |
|
封装后 (BaseRxActivity的子类使用)：1
2
3
4
5
6
7addRxDestroy(Api.getInstance().movieService
.getGankData("Android",1)
.compose(RxSchedulers.io_main())
.compose(handleResult())
.subscribe(httpResult -> adapter.setItems(httpResult.data),
new RxException<>(e ->e.printStackTrace()))
);
4、多页请求封装
实体类：1
2
3
4
5
6
7
8
9
10
11
12/**
* Created by Weiss on 2017/1/20.
*/
public class Gank extends BaseListEntity {
@Override
public Flowable<HttpResult<List<Gank>>> getPage(int page) {
return GankApi.getInstance().service.getGankData(param.get("gank"), page)
.compose(RxSchedulers.io_main());
}
}
实体类继承 BaseListEntity，实现getPage方法即可。
UI视图：1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23public class MainActivityFragment extends BaseRxFragment {
@BindView(R.id.baseRecyclerView)
PtrRecyclerView ptrRecyclerView;
private MultiTypeAdapter adapter;
public MainActivityFragment() {
}
@Override
protected int getLayoutId() {
return R.layout.fragment_main;
}
@Override
protected void initView() {
ptrRecyclerView.setParam("gank","Android");
adapter = new MultiTypeAdapter();
adapter.register(Gank.class,new GankViewProvider());
ptrRecyclerView.setAdapter(adapter,new Gank());
}
}
只需要写一个适配器和实体类，轻松实现多页请求，PtrRecyclerView下拉刷新和上拉加载自动获取数据。
PtrRecyclerView目前只是简单实现下拉刷新和上拉加载，有空会完善，当然例子也会完善。
后记
还可以封装网络加载对话框，这个看个人喜好，同样以上封装同样可以看个人喜好和项目需求自由组装。
RxJava2 + Retrofit2 封装 giithub 地址