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 is passivation and activation in ejb?

913

---

What is stateful session bean?

1034

---

Can beans who are involved in transaction have 'passivation' process?

949

---

What do you mean by in-memory replication?

1032

---

How to increase ejb transaction timeout in weblogic?

1089

---

What is Session Bean Interface?

931

---

Does spring use ejb?

939

---

What are the limitations of using local object?

1079

---

What is EJB server?

1033

---

What does ejb stand for?

1005

---

can u explain about design patterns like singleton,builder,factory

2310

---

What optimization could I use if the ejb container is the only point of write access to the database?

980

---

What is ejb in spring?

885

---

What is the difference between Session bean and Entity bean?one?

1083

---

What is ejb 3?

902

---