Dependency Injection and AOP Brief (eight)--mixed request mode.

2.3. Mixed Request Mode

The previous section mentions that the FQCN (full class name) request pattern brings a poor softness to the dependency definition, so that the pattern of string and full-class name blending has emerged. For example, just the API in spring to declare the injection point example can be changed to use the following API:

Spring string + API with full class name injection Beanfactory injector = new filesystemapplicationcontext ("Depositconfiguration.xml") this. Bank = (Bank) Injector.getbean ("Bank", Bank. Class); Request Name "bank" and a dependency of class bank

In Guice, a more secure, maintainable, annotation-based mixed request pattern is provided, where the identifier is no longer just a string, but a custom Java5 annotation. For example, the previous section cited the setter injection point example, you can implement the hybrid request dependency in the following way:

public class depositor {     Private Bank bank;    //...         @Inject  //bank setter Injection Point     public void Setbank (@BankICBC Bank) {                         // The @BankICBC annotation is a custom annotation that is bound to Bankicbc.class         This . Bank = Bank;    }      //... }

Dependency Injection and AOP Brief (eight)--mixed request mode.