Answer / imtiyaz

Yes i totally agree with the answer of janani,
Now lets dip to one more level

IoC pattern can be implemented in three ways: setter based,
constructor based, and interface based

Setter-Based IoC
This type of IoC uses a setter method to inject the
referenced object into a referring object. This is the most
common type of IoC, and both Spring and PicoContainer
implement it. Setter-based IoC is good for objects that
take optional parameters and objects that need to change
their properties many times during their lifecycles. Its
main disadvantage is that you need to expose all the
properties of an object to the outside world when using a
setter method. This breaks one of the key OO principles:
data encapsulation and information hiding.

Constructor-Based IoC
This type of IoC uses a constructor to set the reference of
the object. Its main advantage is that only the creator
knows about the referenced object. Once the object is
created, the client code that uses the object is unaware of
the referenced object. This approach may not work in all
types of applications, however. For example, if you use an
external API that needs a default constructor, then you
need to go with a setter-based IoC. A constructor-based IoC
is the main type of implementation in Spring.

Interface-Based IoC
In this type of IoC, objects implement a specific interface
from the IoC framework, which the IoC framework will use to
properly inject the objects. One of the main advantages of
this type is that it doesn't need an external configuration
file to configure the object references. Since you need to
use the IoC framework's marker interface, the IoC framework
knows how to glue the objects together. It is similar to
using EJB. Any EJB container knows how to instantiate your
objects and hook them with itself. The main disadvantage of
this approach is that the marker interface ties your
application to a specific IoC framework. Apache Avalon is
based on this approach but this project has been closed.

Answer / janani

Inversion of control or dependency injection, its used to
resolve component dependencies by injecting an instantiated
component to satisfy dependency as opposed to explicitly
requesting a component.There is a saying about this the
servicing component says" don't call us we will call you".
Hence this is called inversion of control. This approach
tightly couples the component with the client code.
The inversion control containers generally control the
creation of objects and resolve dependencies between the
object it manages, example spring framework, hivemind etc.
They support eager instantiation and lazy loading.
Im not familiar with .net, so Please anyone answer the
second question

Explain JSP life cycle?

2 Answers   Accenture,

---

VSS Objectives

1 Answers  

---

when exactly should we use throws ,and wen exactly should we use the try and catch for exceptional handling

0 Answers  

---

What is the use of hashcode in java ?

0 Answers  

---

What is the Spring2.5 MVC Navigation flow?

1 Answers   IBM,

---

---

What do you understand by synchronization? Why is it important?

0 Answers  

---

What is the servletcontext listener and what is JspContext and page context pls tell in simple words.

1 Answers   IBM,

---

my interviewer asked me what technical specification you used how to answer that question

0 Answers  

---

What is the use of the list interface in the java collection? : java collections

0 Answers  

---

What is iterator in the java collections framework? : java collections

0 Answers  

---

What are the different types of classes implemented in the set interfaces? : java collections

0 Answers  

---

what is mean by hasing and maping in java platform and advantage?

0 Answers   CTS,

---