dependency-injection

问题 I am trying to use Dagger 2 for instantiating a Retrofit interface. The CloudContactDataStore class injects the RestClient and calls its methods. When I instantiate a CloudContactDataStore object, its RestClient attribute has null value. public class CloudContactDataStore implements ContactDataStore { @Inject RestClient restClient; public CloudContactDataStore() { this.initializeInjector(); } private void initializeInjector() { ApiComponent component = DaggerApiComponent.builder() .apiModule

问题 I use autofac and can pass parameters to my resolve method. How can I do this using microsofts DependencyResolver interface? 回答1: The IDependencyResolver does not support passing parameters directly, as I'm sure you have noticed. However, since you have Autofac under the hood, you're able to resolve a factory delegate that enables you to pass on parameters to the underlying service: var factory = dependencyResolver.GetService<Func<int, string, IService>>(); var service = factory(5, "42");

问题 I use autofac and can pass parameters to my resolve method. How can I do this using microsofts DependencyResolver interface? 回答1: The IDependencyResolver does not support passing parameters directly, as I'm sure you have noticed. However, since you have Autofac under the hood, you're able to resolve a factory delegate that enables you to pass on parameters to the underlying service: var factory = dependencyResolver.GetService<Func<int, string, IService>>(); var service = factory(5, "42");

问题 Hi I have the following configuration file : @Configuration @PropertySources({ @PropertySource("classpath:english.properties"), @PropertySource("classpath:spanish.properties") }) public class LanguageConfig { @Value(${hello}) private String hello; // getter setter } I want to know if there is a way to Autowire two instances of LanguageConfig , one for each language. Something like : public Myservice() { @Autowire @Qualifier("englishLanguage") private LanguageConfig englishConfig; @Autowire

问题 I am injecting Presenter to BookDashboard (Activity) and BookDashboardPresenter class require an MvpView interface in it's constructor . When i run AppComponent @Component( modules = [ AndroidInjectionModule::class, ActivityBuilder::class ] ) @Singleton interface AppComponent : AndroidInjector<App> { @Component.Builder interface Builder { fun addContext(@BindsInstance context: Context): Builder fun addBookEngine(@BindsInstance bookEngineModule: BookEngineModule) :Builder fun build():

问题 I have a decorator and an associated service that looks like this: public interface IAdditionalDataService<TResult, TModel> { TResult PopulateAdditionalData(TResult model, params Expression<Func<TModel, object>>[] properties); } public class AdditionalDataDecorator<TQuery, TResult, TModel> : IQueryHandler<TQuery, TResult> where TQuery : QueryBase<TResult, TModel>, IQuery<TResult> where TModel : ModelBase { private readonly IQueryHandler<TQuery, TResult> _decorated; private readonly

问题 I have a decorator and an associated service that looks like this: public interface IAdditionalDataService<TResult, TModel> { TResult PopulateAdditionalData(TResult model, params Expression<Func<TModel, object>>[] properties); } public class AdditionalDataDecorator<TQuery, TResult, TModel> : IQueryHandler<TQuery, TResult> where TQuery : QueryBase<TResult, TModel>, IQuery<TResult> where TModel : ModelBase { private readonly IQueryHandler<TQuery, TResult> _decorated; private readonly

问题 In a microservice environment I need to construct a framework for Contract based testing. I'm currently investigatingh how to isolate a single service from it's external dependencies inorder to execute the Provider tests. What I need to do is: Keep the WebApi project intact Start an instance of the WepApi with some config-differences Mock out selected dependencies My Solution structure is this: Case-Solution/ ├── src/ | ├──Case.Api | └──Case.Application ├── test/ | ├──Case.Api.Unittest | ├──

问题 Following on from my question on service locators I have decided to use constructor injection instead. Please consider the following code: <?php interface IAppServiceRegistry { public function getDb(); public function getLogger(); } interface IFooServiceRegistry extends IAppServiceRegistry { public function getFooBarBazModel(); } class AppServiceRegistry implements IAppServiceRegistry, IFooServiceRegistry { private $logger; private $db; private $fooBarBazModel; public function getDb() { //

问题 I am learning AngularJS, and am currently trying master Dependency Injection. When I define a controller, the documentation tells me that specifying dependencies through annotations, and just listing them in the parameter list for the constructor are equivalent. Hence, I should get the same outcome if I write either: angular .module('myapp.controllers', []) .controller('MainNavigationController', ['$scope', '$location', function ($scope, $location) { // ... some code }]); or: angular .module(