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

Is it possible to share an httpsession between a jsp and ejb?

869

---

What is entity bean?

1032

---

What is the procedure of ejb container to handle exceptions?

925

---

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

926

---

How can one EJB be called from within another EJB?

927

---

Name the acid properties of a transaction.

990

---

What is difference between ejb and spring?

936

---

What is ejb and its architecture?

915

---

What is EJB object?

1043

---

Which is more beneficial: Stateful or Stateless Bean?

950

---

What is remote interface in ejb?

910

---

What is ejb application?

904

---

What are the advantages of java beam?

991

---

What is the purpose of ejb in java?

1016

---

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

2288

---