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.
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