Skip to main content

How IOC container works

IOC Container is created in-memory metadata of spring bean. This is ApplicationContext Container.
Memory data checks - are there any beans whose scope is singleton.
write now only one bean is there. So, loads that class, instanstiates it but before
instantiating it will check whether constructor injection is configured or not? Cyclic
dependency injection is configured or not? if both are not configured what is configured
setter injection is configured. Loads the class and creates the object. Completes the
setter injection. Simply what complete the setter injection. After that
it will check- are there any custom-init() method and custom destroy() method
configuration? not there.. IT will check bean class is implementing InitializingBean
and DisposableBean Interfaces? Yes implementing... Automatically it searches
afterPropertiesSet() method is there or not there?
there...these all are done by refraction api. if there is no any exception
is raised then it goes further activity. What is that further activity
that is : Get the bean class objects, then keeps in hashmap and writes that
objects. We use that objects whenever we want.
And what is about destroy() method? ctx.close(); internally application
event is raised. that time it goes to in-memory metadata and checks- is there
any custom destroy() method configuration?  not there.. Checks bean class is
implementing DisposableBean Interface or not? implementing... so automatically
calls destroy() method dynamically.

Comments

Post a Comment

Popular posts from this blog

Mockito interview Questions

1.       Question 1. What Is Mockito? Answer : Mockito allows creation of mock object for the purpose of Test Driven Development and Behavior Driven development. Unlike creating actual object, Mockito allows creation of fake object (external dependencies) which allows it to give consistent results to a given invocation. 2.       Question 2. Why Do We Need Mockito? What Are The Advantages? Answer : Mockito differentiates itself from the other testing framework by removing the expectation beforehand. So, by doing this, it reduces the coupling. Most of the testing framework works on the "expect-run-verify". Mockito allows it to make it "run-verify" framework. Mockito also provides annotation which allows to reduce the boilerplate code. 3.       Question 3. Can You Explain A Mockito Framework? Answer : In Mockito, you always check a particular class. The dependency in that class is injected using m...
2 comments
Read more

REST Methods

GET ============================================= HTTP GET method is used to **read** (or retrieve) a representation of a resource. According to the design of the HTTP specification, GET requests are used only to read data and not change it. Therefore, when used this way, they are considered safe. That is, they can be called without risk of data modification or corruption. Means calling it once has the same effect as calling it 10 times. Additionally, GET is idempotent which means that making multiple identical requests ends up having the same result as a single request. Donot expose unsafe operations via GET. It should never modify any resources on the server. Example: ------------    GET http://www.example.com/customers/12345/orders POST =================================== -> The POST verb is most-often utilized to **create** new resources. In particular, it's used to create subordinate resources. -> That is, subordinate to some other (e.g. parent) reso...
Post a Comment
Read more