Diigo Diary 07/25/2014
Getting Started With Framework7
Java Annotations Tutorial with Custom Annotation | Java Code Geeks
Spring 3.1 M1: Introducing @Profile
4. The IoC container
BeanPostProcessor needs to be instantiated early in order to apply to the initialization of other beans in the context, this early type detection is critical.
Because AOP auto-proxying is implemented as a
BeanPostProcessor itself, neither
BeanPostProcessors nor the beans they reference directly are eligible for auto-proxying, and thus do not have aspects woven into them.
For any such bean, you should see an informational log message: “Bean foo is not eligible for getting processed by all BeanPostProcessor interfaces (for example: not eligible for auto-proxying)“.
ApplicationContext automatically detects any beans that are deployed into it that implement the
BeanFactoryPostProcessor interface. It uses these beans as bean factory post-processors, at the appropriate time. You can deploy these post-processor beans as you would any other bean.
PropertyOverrideConfigurer, another bean factory post-processor, resembles the
PropertyPlaceholderConfigurer, but unlike the latter, the original definitions can have default values or no values at all for bean properties. If an overriding
Properties file does not have an entry for a certain bean property, the default context definition is used.
You can also use
@Autowired for interfaces that are well-known resolvable dependencies:
@Bean is a method-level annotation and a direct analog of the XML
Home: Java Platform, Standard Edition (Java SE) 8 Release 8
Pattern (Java Platform SE 6)
Posted from Diigo. The rest of my favorite links are here.