A lookup method causes the IoC container to override the given methodand return the bean with the name given in the bean attribute. This isa form of Method Injection. It is particularly useful as an alternativeto implementing the BeanFactoryAware interface, in order to be able tomake getBean() calls for non-singleton instances at runtime. In thiscase, Method Injection is a less invasive alternative.
The name of the bean in the current or ancestor factories thatthe lookup method should resolve to. Usually this bean will be aprototype, in which case the lookup method will return a distinctinstance on every invocation. If not specified, the lookup method'sreturn type will be used for a type-based lookup.
The name of the lookup method. This method may have arguments whichwill be passed on to the target constructor or factory method. Notethat for backwards compatibility reasons, in a scenario with overloadednon-abstract methods of the given name, only the no-arg variant of amethod will be turned into a container-driven lookup method.Consider using the @Lookup annotation for more specific demarcation.
The name of the lookup method. This method may have arguments whichwill be passed on to the target constructor or factory method. Notethat for backwards compatibility reasons, in a scenario with overloadednon-abstract methods of the given name, only the no-arg variant of amethod will be turned into a container-driven lookup method.Consider using the @Lookup annotation for more specific demarcation.
The name of the bean in the current or ancestor factories thatthe lookup method should resolve to. Usually this bean will be aprototype, in which case the lookup method will return a distinctinstance on every invocation. If not specified, the lookup method'sreturn type will be used for a type-based lookup.