what is the root interface for accessing a spring bean container?
what is the root interface for accessing a spring bean container? Ne90'dan bulabilirsiniz
BeanFactory (Spring Framework 6.0.3 API)
This is the basic client view of a bean container; further interfaces such as ListableBeanFactory and ConfigurableBeanFactory are available for specific purposes.
This interface is implemented by objects that hold a number of bean definitions, each uniquely identified by a String name. Depending on the bean definition, the factory will return either an independent instance of a contained object (the Prototype design pattern), or a single shared instance (a superior alternative to the Singleton design pattern, in which the instance is a singleton in the scope of the factory). Which type of instance will be returned depends on the bean factory configuration: the API is the same. Since Spring 2.0, further scopes are available depending on the concrete application context (e.g. "request" and "session" scopes in a web environment).
The point of this approach is that the BeanFactory is a central registry of application components, and centralizes configuration of application components (no more do individual objects need to read properties files, for example). See chapters 4 and 11 of "Expert One-on-One J2EE Design and Development" for a discussion of the benefits of this approach.
Note that it is generally better to rely on Dependency Injection ("push" configuration) to configure application objects through setters or constructors, rather than use any form of "pull" configuration like a BeanFactory lookup. Spring's Dependency Injection functionality is implemented using this BeanFactory interface and its subinterfaces.
Normally a BeanFactory will load bean definitions stored in a configuration
source (such as an XML document), and use the org.springframework.beans
package to configure the beans. However, an implementation could simply return
Java objects it creates as necessary directly in Java code. There are no
constraints on how the definitions could be stored: LDAP, RDBMS, XML,
properties file, etc. Implementations are encouraged to support references
amongst beans (Dependency Injection).
In contrast to the methods in ListableBeanFactory, all of the operations in this interface will also check parent factories if this is a HierarchicalBeanFactory. If a bean is not found in this factory instance, the immediate parent factory will be asked. Beans in this factory instance are supposed to override beans of the same name in any parent factory.
Bean factory implementations should support the standard bean lifecycle interfaces as far as possible. The full set of initialization methods and their standard order is:
On shutdown of a bean factory, the following lifecycle methods apply:
Yazı kaynağı : docs.spring.io
4.2 Basics - containers and beans
Inner class names
If for whatever reason you want to configure a bean definition
for a static inner class, you have to use the
binary name of the inner class.
For example, if you have a class called
Foo in the com.example
package, and this Foo class has a
static inner class called
Bar, the value of the
'class' attribute on a bean definition would
be...
com.example.Foo$Bar
Notice the use of the $ character in the
name to separate the inner class name from the outer class
name.
Yazı kaynağı : docs.spring.io
Spring BeanFactory Interface API Guide
All the articles, guides, tutorials(2000 +) written by me so connect with me if you have any questions/queries. Read more about me at About Me.
Top YouTube Channel (75K+ Subscribers): Check out my YouTube channel for free videos and courses - Java Guides YouTube Channel
My Udemy Courses - https://www.udemy.com/user/ramesh-fadatare/
Connect with me on Twitter, Facebook, LinkedIn, GitHub, andStackOverflow
Yazı kaynağı : www.javaguides.net
Yorumların yanıtı sitenin aşağı kısmında
Ali : bilmiyorum, keşke arkadaşlar yorumlarda yanıt versinler.