gpt4 book ai didi

java - 使用带有 AbstractThreadedSyncAdapter 的 RoboGuice 上下文注入(inject)

转载 作者:太空狗 更新时间:2023-10-29 14:28:11 25 4
gpt4 key购买 nike

我正在使用 RoboGuice 2.0b4 连接我的 Android 应用程序,它使用在常规服务中托管的 SyncAdapter(派生自 AbstractThreadedSyncAdapter):

@ContextSingleton
public class SyncAdapter extends AbstractThreadedSyncAdapter {
@Inject
private AccountManager accountManager;

@Inject
public SyncAdapter(Context context) {
super(context, true, false);

Injector injector = RoboGuice.getInjector(context);
ContextScope scope = injector.getInstance(ContextScope.class);
synchronized(ContextScope.class) {
scope.enter(context);
try {
injector.injectMembers(this);
} finally {
scope.exit(context);
}
}
}
[...]
}


@ContextSingleton
public class SynchronizationService extends RoboService {
@Inject
private SyncAdapter syncAdapter;

@Override
public IBinder onBind(Intent intent) {
if (equal("android.content.SyncAdapter", intent.getAction())) {
return syncAdapter.getSyncAdapterBinder();
} else [...]
}
return null;
}
}

不幸的是,当从 SyncAdapter 的构造函数调用 scope.enter 时,RoboGuice 在依赖注入(inject)期间变得递归时退出:

java.lang.IllegalArgumentException: Scope for com.example.SynchronizationService@412c65b0 must be closed before scope for com.example.SynchronizationService@412c65b0 may be opened

当它看到 SynchronizationServiceonCreate 调用附加到当前线程的上下文时。堆栈跟踪:

  at roboguice.inject.ContextScope.enter(ContextScope.java:67)
at roboguice.inject.ContextScopedRoboInjector.getInstance(ContextScopedRoboInjector.java:141)
at com.example.SyncAdapter.<init>(SyncAdapter.java:65)
at java.lang.reflect.Constructor.constructNative(Constructor.java:-1)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:85)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:254)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1031)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at roboguice.inject.ContextScope$1.get(ContextScope.java:126)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:40)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:53)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:110)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:75)
at com.google.inject.internal.MembersInjectorImpl$1.call(MembersInjectorImpl.java:73)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)
at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:73)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:60)
at com.google.inject.internal.InjectorImpl.injectMembers(InjectorImpl.java:944)
at roboguice.inject.ContextScopedRoboInjector.injectMembersWithoutViews(ContextScopedRoboInjector.java:243)
at roboguice.inject.ContextScopedRoboInjector.injectMembers(ContextScopedRoboInjector.java:236)
at roboguice.service.RoboService.onCreate(RoboService.java:57)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:2253)
[...]
at dalvik.system.NativeStart.main(NativeStart.java:-1)

因此,显然,RoboGuice 的依赖注入(inject)是不可重入的。

不幸的是,SyncAdapter 需要基于构造函数的注入(inject),因为 AbstractThreadedSyncAdapter 需要为其构造函数提供上下文。

有什么想法吗?我可能会破解 RoboGuice 以允许重新进入,但这可能不是一件容易的事,所以我更喜欢侵入性较小的解决方法。 ;-)

最佳答案

看起来这实际上是 RoboGuice 中的一个错误。幸运的是,在其问题跟踪器中提交的错误甚至附带了一个补丁:http://code.google.com/p/roboguice/issues/detail?id=179

关于java - 使用带有 AbstractThreadedSyncAdapter 的 RoboGuice 上下文注入(inject),我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/9752249/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com