Answer Posted / rajkumar siripuram

JNDI is the Java Naming and Directory Interface. It's used
to separate the concerns of the application developer and
the application deployer. When you're writing an application
which relies on a database, you shouldn't need to worry
about the user name or password for connecting to that
database. JNDI allows the developer to give a name to a
database, and rely on the deployer to map that name to an
actual instance of the database.

For example, if you're writing code that runs in a Java EE
container, you can write this to get hold of the data source
with JNDI name "Database":


DataSource dataSource = null;
try
{
Context context = new InitialContext();
dataSource = context.lookup("Database");
}
catch (NamingException e)
{
// Couldn't find the data source: give up
}

Note there's nothing here about the database driver, or the
user name, or the password. That is configured inside the
container.

JNDI is not restricted to databases (JDBC); all sorts of
services can be given names. For more details, you should
check out the Sun tutorial on the subject.
link|flag

RAJKUMAR SIRIPURAM

What are the attributes of transaction in ejb?

1028

---

What are the components of session beam?

1121

---

What is ejb and its types?

1044

---

Is ejb a framework?

1015

---

What is ejb container in java?

1005

---

What is an ejb container?

1023

---

What is entity beans in ejb with example?

1035

---

How can one EJB be called from within another EJB?

1033

---

What are ejb containers?

1083

---

What is the use of @ejb annotation?

1027

---

How does the server decide which beans to passivate and activate?

1251

---

Elucidate callback in ejb?

1054

---

What is the default transaction attribute for an ejb?

1042

---

What is ptp model?

1071

---

Can an ejb send asynchronous notifications to its clients?

1038

---