dependency-injection

问题 Spring (and presumably other DI containers, but I'm using Spring) recognises the @DependsOn annotation. You use this to identify any other beans that must be initiated BEFORE this bean, eg @Component @DependsOn({"initiatedFirst", "initiatedSecond"}) public class InitiatedThird { //... Is there an analogous annotation that means that the supplied beans must be initiated AFTER the annotated bean? For example @Component @DependencyOf({"initiatedSecond", "initiatedThird"}) public class

问题 I am using .NET 4.5, Ninject 3 with the binding by convention lib as follow: kernel.Bind(x => x .FromAssembliesMatching("assembly.dll") .SelectAllClasses().InheritedFrom(typeof(ICommandHandler<>)) .BindAllInterfaces()); And this is binding properly for: public class MyCommandHandler : ICommandHandler<MyCommand> But doesn't bind: public class MyGenericCommandHandler<T> : ICommandHandler<MyGenericCommand<T>> However, the previous binding works if I add individual bindings for specific

问题 I have a hazy understanding of GIN, but have it working for injecting presenters, etc. I'm trying to inject a self-made "User" class into all my presenters in order to get the currently logged-in user. I've added @Inject to the constructor on my User class, and added User to my GIN module ... but apart from that, I'm totally lost. Do I bind it to my app presenter (tried that, but I get an error since User doesn't extend my AppPresenter)? As a singleton? Is this even the right way to get pass

问题 I need the authenticated User, to access REST services. My idea is to have an IdentityService that is RequestScoped and can be injected by all REST service clients. The setup is like: Controller -> BusinessLogic -> RESTServiceClient So to passing the User down would involve lots of code. As Guice's @RequestScoped is not supported (https://groups.google.com/forum/#!msg/play-framework/MEOAhdOJz5Q/-cukqS-ZBAAJ) How can this be done with Play? The Problem is also described here (without a

问题 This is a question about dependency injection. When constructing a service object, we pass in collaborators via the constructor in the construction phase. The service object would implement an interface, and that would be called during the run-phase. Sometimes is is difficult to know if a particular object should be passed via the constructor or be part of the interface implemented by the service class? Are there any rules about choosing one option over the other? The question is most

问题 My objective is to run a never ending process in a parallel thread. The problem is, I cannot just instantiate my worker service in the new Thread, because I am using DI in my application. Based on my research here on SO, I have noticed many people are suggesting that Abstract Factories need to be injected into the thread to dynamically instantiate a thread-safe object in a parallel thread. 1, 2 /// <summary> /// Responsible for starting parallel long running worker threads /// </summary>

问题 I'm starting to learn both Java and Spring boot now, and I'm having some problems with dependency injection in integration tests. I have a class under src/main/java/com/rfd/domain/services called TransactionService, which is marked as @Service and which has another dependencies, one of them a repository created by Spring boot. When I launch the application, it is launched correctly so I assume the dependencies are being resolved correctly. This is the summarized class: package com.rfd.domain

问题 Is there a way to bind an injected object to a specific instance using Spring DI similar to Google Guice's bind(MyClass.class).toInstance(myclassobject); 回答1: If the constructor or member variable is annotated with @Autowired , Spring will try to find a bean that matches the type of the Object. You can get similar functionality to the annotation using @Qualifier , for example: bind(MyClass.class).annotatedWith(Names.named("main")).toInstance(myclassobject); would become in Spring: @Autowired

问题 Currently, my code is similar to this (shortened just to make a point): DAL Repository Interface public interface IRepository<TEntity, in TKey> { IList<TEntity> GetAll(); TEntity Get(TKey id); TEntity Add(TEntity item); TEntity Update(TEntity item); bool Remove(TKey id); } Base EF repository public class BaseEFRepository<TEntity, TKey> : IRepository<TEntity, TKey> where TEntity: class, IEntity<TKey> where TKey: struct { protected readonly DbContext _dbContext; public BaseRepository() {

问题 I am reading about SOLID principles and I stopped here on " Dependency inversion principle" which means the objects should passed already instantiated to anther object, which means composition cannot be applied with Dependency inversion principle am right? or there is something I miss? UPDATE ************************************************** suppose you have a class and this class has an attribute which is reference to anther object, we have 2 solution(for me): Create the object outside the